dew-method 0.1.0

package/src/dew-skills/1-analysis/dew-project-brief/assets/project-brief-template.md

@@ -0,0 +1,132 @@
+# DEW Project Brief Template
+
+```markdown
+---
+title: "{Project Name} Project Brief"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "1-analysis"
+stepsCompleted: []
+decisionGates:
+  GATE-00-project-scope:
+    status: pending
+evidence: []
+assumptions: []
+caveats: []
+---
+
+# Project Brief: {Project Name}
+
+## 0. Document Purpose
+
+This brief defines the initial scope, purpose, users, learning goals, and evidence requirements for the data engineering project.
+
+## 1. Project Summary
+
+[What is this project?]
+
+## 2. Project Type
+
+Choose one:
+
+- A. Learning / exploration
+- B. Portfolio project
+- C. Internal decision-support
+- D. Production-grade
+
+Decision:
+
+## 3. Target Users / Data Consumers
+
+Who will use the output?
+
+- Analyst
+- Business user
+- Data scientist
+- Application
+- Farmer / field user
+- External user
+- Other
+
+## 4. Decision Supported
+
+What decision should this data product help users make?
+
+## 5. Expected Data Product
+
+Possible outputs:
+
+- Dashboard
+- Gold data mart
+- API
+- ML feature table
+- Report
+- Notebook
+- Reverse ETL output
+- Web app feature
+
+## 6. MVP Scope
+
+### In Scope
+
+- ...
+
+### Out of Scope
+
+- ...
+
+## 7. Learning Objectives
+
+What should the user learn while building this project?
+
+- Source assessment
+- KPI feasibility
+- Ingestion
+- Storage design
+- Transformation/modeling
+- Serving layer
+- Data quality
+- Governance/DataOps
+
+## 8. Initial KPI Hypotheses
+
+Important: These are hypotheses, not verified KPIs.
+
+| KPI ID | KPI Name | Business Question | Candidate Grain | Status |
+|---|---|---|---|---|
+| KPI-001 | | | | Hypothesis |
+
+## 9. Initial Source Hypotheses
+
+Important: These sources are not accepted until validated.
+
+| Source ID | Source Name | Source Type | Access Method | Status |
+|---|---|---|---|---|
+| SRC-001 | | API/File/DB/Stream | | Candidate |
+
+## 10. Assumptions
+
+- [ASSUMPTION] ...
+
+## 11. Known Unknowns
+
+- ...
+
+## 12. Evidence Required Before Architecture
+
+Before final architecture, DEW requires:
+
+- KPI feasibility evidence
+- source access evidence
+- source sample/schema evidence
+- grain decision
+- trust expectation decision
+- freshness decision
+
+## 13. Next Recommended Workflow
+
+Recommended next skill:
+
+`dew-business-discovery`

package/src/dew-skills/1-analysis/dew-project-brief/assets/project-brief-validation-rubric.md

@@ -0,0 +1,30 @@
+# Project Brief Validation Rubric
+
+## Decision Readiness
+
+- Does the brief identify the project type?
+- Does it identify target users or data consumers?
+- Does it identify the decision supported?
+- Does it distinguish assumptions from facts?
+
+## Data Engineering Readiness
+
+- Does it list initial KPI hypotheses?
+- Does it list initial source hypotheses?
+- Does it avoid claiming KPI/source feasibility prematurely?
+- Does it state what evidence is required before architecture?
+
+## Learning Readiness
+
+- Does it include learning objectives?
+- Does it identify which FDE lifecycle concepts the project will practice?
+- Does it create useful next steps?
+
+## Failure Conditions
+
+The brief fails validation if:
+- it jumps directly to architecture/tooling
+- it treats unverified sources as accepted
+- it treats KPI hypotheses as verified
+- it lacks target consumer or decision context
+- it has no MVP boundary

package/src/dew-skills/1-analysis/dew-project-brief/checklist.md

@@ -0,0 +1,15 @@
+# Project Brief Checklist
+
+- [ ] Project type selected.
+- [ ] Target consumer identified.
+- [ ] Business decision identified.
+- [ ] Expected data product described.
+- [ ] MVP scope defined.
+- [ ] Non-goals defined.
+- [ ] Learning objectives included.
+- [ ] KPI hypotheses listed but not marked verified.
+- [ ] Source hypotheses listed but not marked accepted.
+- [ ] Assumptions labeled.
+- [ ] Evidence required before architecture listed.
+- [ ] Decision log updated.
+- [ ] Learning log updated if learning mode is enabled.

package/src/dew-skills/1-analysis/dew-project-brief/customize.toml

@@ -0,0 +1,26 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-project-brief.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+brief_template = "assets/project-brief-template.md"
+validation_rubric = "assets/project-brief-validation-rubric.md"
+checklist = "checklist.md"
+
+brief_output_path = "{planning_artifacts}/project-briefs"
+run_folder_pattern = "project-brief-{project_name}-{date}"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"

package/src/dew-skills/2-plan-workflows/dew-data-product-prd/SKILL.md

@@ -0,0 +1,106 @@
+---
+name: dew-data-product-prd
+description: Create, update, or validate a data product PRD with consumers, KPI hypotheses, grain, freshness, trust expectation, known limitations, and evidence requirements.
+---
+
+# DEW Data Product PRD
+
+**Goal:** Create a data product PRD that is clear enough for KPI feasibility, source validation, and later architecture.
+
+**Your Role:** You are a data product manager facilitator.
+
+You help the user define what data product should exist, who uses it, what decisions it supports, and what must be validated before architecture.
+
+## Mandatory Rules
+
+- Do not finalize architecture.
+- Do not mark KPI/source feasibility as verified.
+- Do not hide assumptions.
+- Trust expectation must be explicitly selected.
+- Grain and freshness must be stated or marked pending.
+- The PRD must state what evidence is required before architecture.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.prd_template}`
+   - `{workflow.validation_rubric}`
+6. Greet user in configured language.
+
+## Intent Modes
+
+### Create
+
+Create a new data product PRD.
+
+Bind `{doc_workspace}` to:
+
+`{workflow.prd_output_path}/{workflow.run_folder_pattern}/`
+
+Create:
+- `data-product-prd.md`
+- `addendum.md` if needed
+- `.decision-log.md` if missing
+
+### Update
+
+Update an existing PRD based on new decision, new KPI, source change, scope change, or validation finding.
+
+### Validate
+
+Review PRD against the validation rubric.
+
+Do not edit unless user asks.
+
+## Discovery
+
+Load available inputs:
+- project brief
+- business discovery
+- KPI catalog
+- KPI-source matrix
+- decision log
+- learning log
+
+If missing, continue only with caveats or ask user to run previous skill.
+
+## Required Decision Gates
+
+### Trust Expectation Gate
+
+Ask user to choose:
+
+A. Exploratory only  
+B. Internal decision-support with documented limitations  
+C. Trusted shared product with quality checks  
+D. Production-grade with contracts and monitoring  
+
+Do not continue until user chooses.
+
+### Grain Gate
+
+Ask user to approve or mark pending:
+- product grain
+- KPI grain
+- serving grain
+
+### Freshness Gate
+
+Ask user to approve or mark pending:
+- expected freshness
+- minimum acceptable freshness
+- source freshness still to validate
+
+## Finalize
+
+Before finalizing:
+- run checklist
+- record trust decision
+- record grain/freshness assumptions
+- state evidence required before architecture
+- set PRD status to final or draft-with-caveats
+- recommend next: `dew-kpi-feasibility` and `dew-source-validation`

package/src/dew-skills/2-plan-workflows/dew-data-product-prd/assets/data-product-prd-template.md

@@ -0,0 +1,122 @@
+# Data Product PRD Template
+
+```markdown
+---
+title: "{Project Name} Data Product PRD"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "2-plan-workflows"
+decisionGates:
+  GATE-05-trust-expectation:
+    status: pending
+  GATE-04-kpi-grain:
+    status: pending
+evidence: []
+assumptions: []
+caveats:
+  - "KPI and source feasibility must be validated before architecture."
+---
+
+# Data Product PRD: {Project Name}
+
+## 0. Document Purpose
+
+This PRD defines the data product requirements.
+
+It does not prove KPI or source feasibility. Those must be validated in later workflows.
+
+## 1. Vision
+
+## 2. Data Consumers
+
+| Consumer ID | Consumer | Role | Decision Supported | Output Needed |
+|---|---|---|---|---|
+| CON-001 | | | | |
+
+## 3. Decisions Supported
+
+## 4. Data Product Type
+
+Choose one or more:
+
+- Dashboard
+- Gold data mart
+- API
+- ML feature table
+- Report
+- Notebook
+- Web app feature
+- Reverse ETL output
+
+## 5. KPI Hypotheses
+
+| KPI ID | KPI Name | Formula Summary | Grain | Feasibility Status |
+|---|---|---|---|---|
+| KPI-001 | | | | Hypothesis |
+
+## 6. Product Grain
+
+One row / one observation represents:
+
+## 7. Freshness Requirement
+
+Expected freshness:
+
+Minimum acceptable freshness:
+
+Freshness validation status:
+
+## 8. Trust Expectation
+
+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:
+
+## 9. Candidate Sources
+
+| Source ID | Source Name | Source Type | Role | Validation Status |
+|---|---|---|---|---|
+| SRC-001 | | API/File/DB | Required/Optional | Candidate |
+
+## 10. Data Quality Expectations
+
+Initial expectations only. Final DQ rules come later.
+
+- Completeness:
+- Uniqueness:
+- Valid ranges:
+- Freshness:
+- Referential integrity:
+- Business rule consistency:
+
+## 11. Known Limitations
+
+## 12. Non-Goals
+
+## 13. Evidence Required Before Architecture
+
+Architecture cannot be finalized until:
+
+- primary KPI feasibility is validated or caveated
+- P1 sources are access-verified
+- source sample/schema evidence exists
+- grain is approved
+- trust expectation is approved
+- freshness expectation is approved
+
+## 14. Open Questions
+
+## 15. Assumptions Index
+
+## 16. Next Workflows
+
+Required next:
+- `dew-kpi-feasibility`
+- `dew-source-validation`

package/src/dew-skills/2-plan-workflows/dew-data-product-prd/assets/data-product-prd-validation-rubric.md

@@ -0,0 +1,33 @@
+# Data Product PRD Validation Rubric
+
+## Consumer and Decision Readiness
+
+- Does the PRD identify data consumers?
+- Does it identify the decisions supported?
+- Does each KPI map to a decision?
+- Does it define the data product type?
+
+## Data Product Readiness
+
+- Does it state product grain?
+- Does it state freshness requirement?
+- Does it state trust expectation?
+- Does it identify candidate sources?
+
+## Evidence Discipline
+
+- Does it avoid marking KPI feasibility as verified?
+- Does it avoid marking sources as accepted without validation?
+- Does it list evidence required before architecture?
+- Does it clearly label assumptions and caveats?
+
+## Failure Conditions
+
+The PRD fails if:
+- it jumps to architecture
+- it claims source/KPI feasibility without evidence
+- trust expectation is missing
+- grain is missing with no pending decision
+- freshness is missing with no pending decision
+- consumers are vague
+- KPIs do not map to decisions

package/src/dew-skills/2-plan-workflows/dew-data-product-prd/checklist.md

@@ -0,0 +1,19 @@
+# Data Product PRD Checklist
+
+- [ ] Project brief loaded or context provided.
+- [ ] Business discovery loaded or context provided.
+- [ ] KPI catalog loaded or KPI hypotheses captured.
+- [ ] Data consumers defined.
+- [ ] Decisions supported defined.
+- [ ] Data product type selected.
+- [ ] KPI hypotheses listed.
+- [ ] Product grain stated or marked pending.
+- [ ] Freshness requirement stated or marked pending.
+- [ ] Trust expectation selected.
+- [ ] Candidate sources listed.
+- [ ] Known limitations documented.
+- [ ] Evidence required before architecture listed.
+- [ ] Assumptions labeled.
+- [ ] Caveats labeled.
+- [ ] Decision log updated.
+- [ ] Learning log updated if learning mode is enabled.

package/src/dew-skills/2-plan-workflows/dew-data-product-prd/customize.toml

@@ -0,0 +1,29 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-data-product-prd.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/brief.md",
+  "file:{project-root}/**/business-discovery.md",
+  "file:{project-root}/**/kpi-catalog.md",
+  "file:{project-root}/**/kpi-source-matrix.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+prd_template = "assets/data-product-prd-template.md"
+validation_rubric = "assets/data-product-prd-validation-rubric.md"
+checklist = "checklist.md"
+
+prd_output_path = "{planning_artifacts}/data-product-prds"
+run_folder_pattern = "data-product-prd-{project_name}-{date}"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"

package/src/dew-skills/2-plan-workflows/dew-kpi-feasibility/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: dew-kpi-feasibility
+description: Validate whether candidate KPIs can be computed from available fields, samples, and source evidence before architecture.
+---
+
+# DEW KPI Feasibility
+
+**Goal:** Validate whether candidate KPIs can actually be computed from available data before architecture and implementation proceed.
+
+**Your Role:** You are a KPI feasibility facilitator and data validation planner.
+
+You do not merely document KPI ideas. You force KPI definitions to confront real data availability, grain, source fields, and sample computation requirements.
+
+## 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 KPI feasibility workflow.
+
+## 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 mark KPI as feasible without evidence.
+- Update frontmatter after each completed step.
+
+## Mandatory Rules
+
+- KPI definitions are hypotheses until validated.
+- A KPI is not feasible just because a formula exists.
+- A KPI is not feasible unless required fields, grain, and sample computation are validated or explicitly caveated.
+- Do not proceed to architecture if primary KPI feasibility is missing.
+- If evidence is missing, trigger `HALT-03 — KPI Feasibility Not Proven` or `HALT-18 — No Validation Evidence`.
+- The agent may recommend, but must not decide.
+
+## 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 `{workflow.activation_steps_prepend}`.
+
+3. Load persistent facts from `{workflow.persistent_facts}`.
+
+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.feasibility_report_template}`
+   - `{workflow.field_availability_template}`
+   - `{workflow.sample_computation_plan_template}`
+   - `{workflow.status_rubric}`
+
+6. Greet `{user_name}` in `{communication_language}`.
+
+7. Execute `{workflow.activation_steps_append}`.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-init.md`

package/src/dew-skills/2-plan-workflows/dew-kpi-feasibility/assets/field-availability-template.md

@@ -0,0 +1,43 @@
+
+---
+
+## `assets/field-availability-template.md`
+
+```markdown
+# Field Availability Template
+
+```markdown
+# Field Availability Report
+
+## KPI
+
+KPI ID:
+
+KPI Name:
+
+## Required Fields
+
+| Required Field | Business Meaning | Required? | Candidate Source | Candidate Source Field | Available? | Evidence Path | Notes |
+|---|---|---|---|---|---|---|---|
+| | | Yes/No | | | Unknown/Yes/No | | |
+
+## Field Meaning Check
+
+| Field | Expected Meaning | Observed Meaning | Match? | Notes |
+|---|---|---|---|---|
+| | | | Yes/No/Unknown | |
+
+## Missing Fields
+
+| Required Field | Impact | Possible Substitute | Decision Needed |
+|---|---|---|---|
+| | | | Yes/No |
+
+## Field Availability Status
+
+Choose one:
+
+- Complete
+- Partial
+- Missing critical fields
+- Unknown