dew-method 0.1.0

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: dew-requirement-gate
+description: Review KPI feasibility, source validation, trust, grain, freshness, caveats, and MVP scope before allowing architecture.
+---
+
+# DEW Requirement Gate
+
+**Goal:** Decide whether the project is ready to proceed to data architecture.
+
+**Your Role:** You are a DEW readiness facilitator.
+
+You do not create architecture here. You audit whether architecture is safe to start.
+
+You may recommend, but you must not decide.
+
+## Workflow Architecture
+
+This workflow uses step-file architecture.
+
+Rules:
+- Read one step file at a time.
+- Read the complete step file before acting.
+- Do not skip steps.
+- Do not load future steps early.
+- Stop at decision gates.
+- Do not approve architecture readiness without user decision.
+- Update frontmatter after each completed step.
+
+## Conventions
+
+- Bare paths resolve from the skill root.
+- `{skill-root}` resolves to this skill's installed directory.
+- `{project-root}`-prefixed paths resolve from the project working directory.
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table.
+- `{doc_workspace}` is the run folder for this workflow.
+
+## Mandatory Rules
+
+- Do not create architecture in this skill.
+- Do not allow architecture if primary KPI feasibility is unresolved.
+- Do not allow architecture if P1 source validation is unresolved.
+- Do not hide caveats.
+- Do not treat user-approved caveats as evidence.
+- Do not proceed past architecture readiness gate without explicit user choice.
+- If KPI feasibility is missing, trigger `HALT-03 — KPI Feasibility Not Proven`.
+- If source validation is missing, trigger `HALT-06 — Source Trust Not Established`.
+- If grain is undefined, trigger `HALT-07 — Grain Undefined`.
+- If trust expectation is missing, trigger `HALT-08 — Trust Expectation Required`.
+- If freshness is unverified, trigger `HALT-09 — Freshness Unverified`.
+- If architecture is requested too early, trigger `HALT-10 — Architecture Before Validation`.
+- If evidence is missing, trigger `HALT-18 — No Validation Evidence`.
+
+## On Activation
+
+1. Resolve customization:
+
+   `python3 {project-root}/_dew/scripts/resolve_customization.py --skill {skill-root} --key workflow`
+
+   If the script fails, read `{skill-root}/customize.toml` directly and use defaults.
+
+2. Execute each entry in `{workflow.activation_steps_prepend}` in order.
+
+3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}`.
+
+4. Load `{project-root}/_dew/dew/config.yaml` if present and resolve:
+   - `{user_name}`
+   - `{project_name}`
+   - `{communication_language}`
+   - `{document_output_language}`
+   - `{planning_artifacts}`
+   - `{implementation_artifacts}`
+   - `{evidence_artifacts}`
+   - `{learning_artifacts}`
+   - `{learning_mode}`
+
+5. Load:
+   - `{workflow.gate_report_template}`
+   - `{workflow.readiness_rubric}`
+   - `{workflow.caveat_register_template}`
+   - `{workflow.architecture_readiness_matrix_template}`
+   - `{workflow.decision_options}`
+
+6. Greet `{user_name}` in `{communication_language}`.
+
+7. Execute each entry in `{workflow.activation_steps_append}` in order.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-init.md`

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/assets/architecture-readiness-matrix-template.md

@@ -0,0 +1,24 @@
+# Architecture Readiness Matrix Template
+
+```markdown
+# Architecture Readiness Matrix
+
+| Readiness Item | Required? | Status | Evidence | Gate | Notes |
+|---|---|---|---|---|---|
+| Business decision clear | Yes | Ready/Caveated/Blocked | | GATE-02 | |
+| Data consumer clear | Yes | Ready/Caveated/Blocked | | GATE-01 | |
+| Primary KPI feasible or caveated | Yes | Ready/Caveated/Blocked | | GATE-06 | |
+| P1 sources validated or caveated | Yes | Ready/Caveated/Blocked | | GATE-08 | |
+| Trust expectation approved | Yes | Ready/Caveated/Blocked | | GATE-05 | |
+| Grain approved | Yes | Ready/Caveated/Blocked | | GATE-04/GATE-09 | |
+| Freshness approved | Yes | Ready/Caveated/Blocked | | GATE-10 | |
+| Schema evolution direction known | Yes | Ready/Caveated/Blocked | | GATE-11 | |
+| Evidence indexed | Yes | Ready/Caveated/Blocked | | HALT-18 | |
+| Caveats accepted | Yes if caveats exist | Ready/Caveated/Blocked | | | |
+
+## Final Architecture Readiness
+
+A. Ready  
+B. Ready with caveats  
+C. Blocked  
+D. Scope reduction needed  

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/assets/caveat-register-template.md

@@ -0,0 +1,50 @@
+# Caveat Register Template
+
+```markdown
+# Caveat Register
+
+## Purpose
+
+This register captures accepted limitations before architecture begins.
+
+Accepted caveats are not evidence. They are known risks that must be preserved downstream.
+
+## Caveat Table
+
+| Caveat ID | Area | Description | Severity | Accepted By User? | Downstream Impact | Revisit Trigger |
+|---|---|---|---|---|---|---|
+| CAV-001 | KPI | | High/Medium/Low | Yes/No | | |
+
+## Caveat Entry Template
+
+## CAV-{number} — {Short Name}
+
+Area:
+- Business
+- KPI
+- Source
+- Trust
+- Grain
+- Freshness
+- DQ
+- Governance
+- Architecture
+
+Description:
+
+Severity:
+
+Why accepted:
+
+Downstream impact:
+- Architecture:
+- Storage:
+- Ingestion:
+- Transformation:
+- Serving:
+- Monitoring:
+- Documentation:
+
+Revisit trigger:
+
+Owner:

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/assets/requirement-gate-decision-options.md

@@ -0,0 +1,72 @@
+# Requirement Gate Decision Options
+
+## A. Proceed to architecture
+
+Use when:
+- KPI readiness is sufficient
+- source readiness is sufficient
+- trust, grain, and freshness are approved
+- caveats are minor or none
+- evidence is indexed
+
+Meaning:
+Architecture can begin normally.
+
+## B. Proceed to architecture with caveats
+
+Use when:
+- some evidence is partial
+- risks are understood
+- user accepts caveats
+- downstream impact is documented
+
+Meaning:
+Architecture can begin, but must carry caveats explicitly.
+
+Required:
+- caveat register updated
+- decision log updated
+- architecture artifact must include caveats
+
+## C. Return to KPI validation
+
+Use when:
+- primary KPI is still hypothesis only
+- required fields are unverified
+- formula or grain is unclear
+- sample computation is missing
+
+Meaning:
+Do not start architecture.
+
+Recommended workflows:
+- dew-kpi-feasibility
+- dew-kpi-prototype
+- dew-kpi-validation-review
+
+## D. Return to source validation
+
+Use when:
+- P1 source access is unverified
+- sample/schema is missing
+- source grain/freshness is unknown
+- source trust is not established
+
+Meaning:
+Do not start architecture.
+
+Recommended workflows:
+- dew-source-validation
+- dew-source-access-check
+- dew-source-sampler
+- dew-source-contract-test
+
+## E. Reduce MVP scope
+
+Use when:
+- current MVP depends on unresolved KPI/source
+- simpler scope can proceed safely
+- user prefers progress over full scope
+
+Meaning:
+Update PRD/KPI/source scope before architecture.

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/assets/requirement-gate-report-template.md

@@ -0,0 +1,254 @@
+# Requirement Gate Report Template
+
+```markdown
+---
+title: "{Project Name} Requirement Gate Report"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "2-plan-workflows"
+stepsCompleted: []
+decisionGates:
+  GATE-05-trust-expectation:
+    status: pending
+  GATE-04-kpi-grain:
+    status: pending
+  GATE-10-source-freshness:
+    status: pending
+  GATE-12-architecture-readiness:
+    status: pending
+evidence: []
+assumptions: []
+caveats: []
+architectureReadiness:
+  status: pending
+---
+
+# Requirement Gate Report: {Project Name}
+
+## 0. Document Purpose
+
+This report decides whether the project is ready to proceed to data architecture.
+
+This document does not create architecture.
+
+It reviews:
+- business readiness
+- KPI readiness
+- source readiness
+- trust expectation
+- grain
+- freshness
+- caveats
+- MVP scope
+- architecture readiness
+
+## 1. Input Artifacts
+
+| Artifact | Path | Loaded? | Status | Notes |
+|---|---|---|---|---|
+| Project Brief | | Yes/No | | |
+| Business Discovery | | Yes/No | | |
+| Data Product PRD | | Yes/No | | |
+| KPI Catalog | | Yes/No | | |
+| KPI Feasibility Report | | Yes/No | | |
+| Source Inventory | | Yes/No | | |
+| Source Scorecard | | Yes/No | | |
+| Source Validation Report | | Yes/No | | |
+| Evidence Index | | Yes/No | | |
+| Decision Log | | Yes/No | | |
+| Learning Log | | Yes/No | | |
+
+## 2. Executive Readiness Summary
+
+| Area | Status | Blocker? | Notes |
+|---|---|---|---|
+| Business decision | Ready / Caveated / Blocked | Yes/No | |
+| Data consumer | Ready / Caveated / Blocked | Yes/No | |
+| KPI feasibility | Ready / Caveated / Blocked | Yes/No | |
+| Source validation | Ready / Caveated / Blocked | Yes/No | |
+| Trust expectation | Ready / Caveated / Blocked | Yes/No | |
+| Grain | Ready / Caveated / Blocked | Yes/No | |
+| Freshness | Ready / Caveated / Blocked | Yes/No | |
+| Evidence index | Ready / Caveated / Blocked | Yes/No | |
+| Caveats accepted | Ready / Caveated / Blocked | Yes/No | |
+
+## 3. Business Readiness
+
+### Data Consumer
+
+### Decision Supported
+
+### Data Product Type
+
+### Status
+
+- Ready
+- Ready with caveats
+- Blocked
+
+### Notes
+
+## 4. KPI Readiness
+
+| KPI ID | KPI Name | Priority | Feasibility Status | Evidence | Architecture Impact |
+|---|---|---|---|---|---|
+| KPI-001 | | Primary/Secondary | | | |
+
+### KPI Blockers
+
+- ...
+
+### KPI Caveats
+
+- ...
+
+### KPI Decision Needed
+
+A. Accept KPI readiness  
+B. Accept KPI readiness with caveats  
+C. Return to KPI validation  
+D. Defer KPI  
+E. Reduce MVP scope  
+
+## 5. Source Readiness
+
+| Source ID | Source Name | Related KPI | Validation Status | Evidence | Architecture Impact |
+|---|---|---|---|---|---|
+| SRC-001 | | | P1/P2/Exploration/Rejected/Blocked | | |
+
+### Source Blockers
+
+- ...
+
+### Source Caveats
+
+- ...
+
+### Source Decision Needed
+
+A. Accept source readiness  
+B. Accept source readiness with caveats  
+C. Return to source validation  
+D. Defer source  
+E. Reduce MVP scope  
+
+## 6. Trust Expectation Gate
+
+Choose one:
+
+A. Exploratory only  
+B. Internal decision-support with documented limitations  
+C. Trusted shared product with quality checks  
+D. Production-grade with contracts and monitoring  
+
+Selected:
+
+Rationale:
+
+Evidence / context:
+
+Downstream impact:
+- architecture:
+- DQ:
+- serving:
+- monitoring:
+- documentation:
+
+## 7. Grain Gate
+
+### Product Grain
+
+One row / observation represents:
+
+### KPI Grain(s)
+
+| KPI ID | Grain | Status | Notes |
+|---|---|---|---|
+
+### Source Grain(s)
+
+| Source ID | Grain | Compatibility | Notes |
+|---|---|---|---|
+
+### Grain Decision
+
+A. Grain is consistent enough for architecture  
+B. Grain is consistent with caveats  
+C. Requires bridge/mapping design  
+D. Return to KPI/source validation  
+E. Reduce MVP scope  
+
+Selected:
+
+## 8. Freshness Gate
+
+### Required Freshness
+
+### Observed Source Freshness
+
+| Source ID | Required | Observed | Status | Notes |
+|---|---|---|---|---|
+
+### Freshness Decision
+
+A. Freshness is sufficient  
+B. Freshness is acceptable with caveats  
+C. Freshness is insufficient; redesign requirement  
+D. Return to source validation  
+E. Reduce MVP scope  
+
+Selected:
+
+## 9. Caveat Register
+
+| Caveat ID | Area | Description | Severity | Accepted? | Downstream Impact |
+|---|---|---|---|---|---|
+| CAV-001 | KPI/Source/Trust/Grain/Freshness | | High/Medium/Low | Yes/No | |
+
+## 10. Architecture Readiness Matrix
+
+| Requirement | Status | Evidence | Decision |
+|---|---|---|---|
+| Primary KPI feasible or caveated | | | |
+| P1 source validated or caveated | | | |
+| Trust expectation approved | | | |
+| Grain approved | | | |
+| Freshness approved | | | |
+| Caveats accepted | | | |
+| Evidence indexed | | | |
+
+## 11. Final Requirement Gate Decision
+
+Choose one:
+
+A. Proceed to architecture  
+B. Proceed to architecture with caveats  
+C. Return to KPI validation  
+D. Return to source validation  
+E. Reduce MVP scope  
+
+Selected:
+
+Reason:
+
+## 12. Decision Log Entries
+
+## 13. Learning Notes
+
+## 14. Next Workflow
+
+If approved:
+
+`dew-data-architecture`
+
+If not approved:
+
+- `dew-kpi-feasibility`
+- `dew-kpi-prototype`
+- `dew-kpi-validation-review`
+- `dew-source-validation`
+- `dew-source-access-check`
+- `dew-source-sampler`
+- `dew-source-contract-test`

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/assets/requirement-readiness-rubric.md

@@ -0,0 +1,37 @@
+# Requirement Readiness Rubric
+
+## Ready
+
+Use when:
+- required artifact exists
+- evidence exists
+- decision gate is approved
+- caveats are minor or accepted
+- no hard HALT remains
+
+## Ready with caveats
+
+Use when:
+- evidence is partial but sufficient for next phase
+- caveats are explicit
+- user accepts caveats
+- downstream impact is documented
+- revisit trigger is defined
+
+## Blocked
+
+Use when:
+- primary KPI is still hypothesis only
+- P1 source is not validated
+- trust expectation is missing
+- grain is undefined
+- freshness is unknown and material
+- evidence is missing
+- hard HALT remains unresolved
+
+## Not applicable
+
+Use when:
+- item is outside MVP scope
+- user explicitly deferred it
+- decision is logged

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/checklist.md

@@ -0,0 +1,75 @@
+# Requirement Gate Checklist
+
+## Required input artifacts
+
+- [ ] Project brief loaded or context provided.
+- [ ] Business discovery loaded or context provided.
+- [ ] Data product PRD loaded or context provided.
+- [ ] KPI catalog loaded.
+- [ ] KPI feasibility report loaded.
+- [ ] Source inventory loaded.
+- [ ] Source validation report loaded.
+- [ ] Evidence index loaded or missing evidence recorded.
+- [ ] Decision log loaded or initialized.
+- [ ] Learning log loaded or initialized.
+
+## Business readiness
+
+- [ ] Data consumer is clear.
+- [ ] Business decision is clear.
+- [ ] Data product type is clear.
+- [ ] MVP scope is clear.
+
+## KPI readiness
+
+- [ ] Primary KPIs identified.
+- [ ] Primary KPIs have feasibility status.
+- [ ] Primary KPIs are not silently treated as verified.
+- [ ] KPI caveats are listed.
+- [ ] KPI blockers are listed.
+- [ ] User has approved KPI readiness or return path.
+
+## Source readiness
+
+- [ ] P1/P2 candidates identified.
+- [ ] P1 sources have access/sample/schema evidence or caveat.
+- [ ] Source caveats are listed.
+- [ ] Source blockers are listed.
+- [ ] User has approved source readiness or return path.
+
+## Trust, grain, freshness
+
+- [ ] Trust expectation selected.
+- [ ] Product/KPI grain approved or caveated.
+- [ ] Source grain compatibility reviewed.
+- [ ] Freshness requirement reviewed.
+- [ ] Observed source freshness reviewed or caveated.
+- [ ] Schema evolution direction known or caveated.
+
+## Caveat handling
+
+- [ ] Caveat register created.
+- [ ] High severity caveats are explicitly approved or block the gate.
+- [ ] Downstream impact documented.
+- [ ] Revisit triggers defined.
+
+## Architecture readiness
+
+- [ ] Architecture readiness matrix completed.
+- [ ] Final gate decision selected by user.
+- [ ] Decision log updated.
+- [ ] Learning log updated if learning mode is enabled.
+- [ ] Evidence index referenced.
+- [ ] No unresolved hard HALT remains.
+
+## Failure conditions
+
+Fail this gate if:
+- architecture readiness is approved without user choice
+- primary KPI is unresolved with no caveat
+- P1 source is unresolved with no caveat
+- trust expectation is missing
+- grain is undefined
+- freshness is material and unknown
+- evidence is missing and not caveated
+- caveats are hidden

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/customize.toml

@@ -0,0 +1,44 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-requirement-gate.
+#
+# Override files:
+#   {project-root}/_dew/custom/dew-requirement-gate.toml
+#   {project-root}/_dew/custom/dew-requirement-gate.user.toml
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "file:{project-root}/**/brief.md",
+  "file:{project-root}/**/business-discovery.md",
+  "file:{project-root}/**/data-product-prd.md",
+  "file:{project-root}/**/kpi-catalog.md",
+  "file:{project-root}/**/kpi-source-matrix.md",
+  "file:{project-root}/**/kpi-feasibility-report.md",
+  "file:{project-root}/**/source-inventory.md",
+  "file:{project-root}/**/source-scorecard.md",
+  "file:{project-root}/**/source-validation-report.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+gate_report_template = "assets/requirement-gate-report-template.md"
+readiness_rubric = "assets/requirement-readiness-rubric.md"
+caveat_register_template = "assets/caveat-register-template.md"
+architecture_readiness_matrix_template = "assets/architecture-readiness-matrix-template.md"
+decision_options = "assets/requirement-gate-decision-options.md"
+checklist = "checklist.md"
+
+gate_output_path = "{planning_artifacts}/requirement-gate"
+run_folder_pattern = "requirement-gate-{project_name}-{date}"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"
+evidence_index_path = "{evidence_artifacts}/validation-evidence-index.md"

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-01-init.md

@@ -0,0 +1,60 @@
+# Step 01 — Requirement Gate Initialization
+
+## Mandatory Rules
+
+- Do not create architecture in this step.
+- Do not approve architecture readiness in this step.
+- Read the complete step before acting.
+- Initialize document state before moving to next step.
+
+## Task
+
+Initialize the Requirement Gate workflow.
+
+## Sequence
+
+### 1. Detect existing workflow
+
+Look for existing requirement gate report in:
+
+- `{workflow.gate_output_path}/**/requirement-gate-report.md`
+- `{planning_artifacts}/**/*requirement*gate*.md`
+
+If an unfinished report exists, offer to resume.
+
+### 2. Create workspace
+
+If fresh workflow, bind `{doc_workspace}` to:
+
+`{workflow.gate_output_path}/{workflow.run_folder_pattern}/`
+
+Create:
+
+- `requirement-gate-report.md`
+- `caveat-register.md`
+- `architecture-readiness-matrix.md`
+
+Use:
+- `{workflow.gate_report_template}`
+- `{workflow.caveat_register_template}`
+- `{workflow.architecture_readiness_matrix_template}`
+
+### 3. Initialize frontmatter
+
+Set:
+
+```yaml
+status: draft
+stepsCompleted:
+  - step-01-init
+decisionGates:
+  GATE-05-trust-expectation:
+    status: pending
+  GATE-04-kpi-grain:
+    status: pending
+  GATE-10-source-freshness:
+    status: pending
+  GATE-12-architecture-readiness:
+    status: pending
+architectureReadiness:
+  status: pending