dew-method 0.1.0

package/src/dew-skills/4-implementation/dew-installation-guide/steps/step-03-create-installation-guide.md

@@ -0,0 +1,29 @@
+# Step 03 — Create Installation Guide
+
+## Mandatory Rules
+
+- Separate verified steps from assumed steps.
+- Include verification step.
+- Include known caveats.
+
+## Task
+
+Create:
+- prerequisites
+- install options
+- config
+- verify installation
+- first run
+- upgrade notes
+- caveats
+
+## Update
+
+Update:
+- installation-guide.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to create usage guide`

package/src/dew-skills/4-implementation/dew-installation-guide/steps/step-04-create-usage-guide.md

@@ -0,0 +1,31 @@
+# Step 04 — Create Usage Guide
+
+## Mandatory Rules
+
+- Usage flow must match module-help.csv.
+- Explain gates and HALTs.
+- Explain artifact locations.
+
+## Task
+
+Create:
+- recommended workflow
+- command reference
+- project modes
+- HALT handling
+- gates
+- common workflows
+- troubleshooting
+
+## Update
+
+Update:
+- usage-guide.md
+- command-reference.md
+- troubleshooting.md
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to installation doc gate`

package/src/dew-skills/4-implementation/dew-installation-guide/steps/step-05-installation-doc-gate.md

@@ -0,0 +1,37 @@
+# Step 05 — Installation Documentation Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- User must approve install docs.
+- Missing verification step blocks approval.
+
+## Decision options
+
+A. Installation docs approved  
+B. Approved with caveats  
+C. Needs revision  
+D. Block install docs  
+
+## Required summary
+
+| Area | Status | Finding |
+|---|---|---|
+| prerequisites | | |
+| install options | | |
+| verification | | |
+| first run | | |
+| usage flow | | |
+| troubleshooting | | |
+
+## User decision
+
+Ask user to choose A/B/C/D.
+
+Do not continue until user chooses.
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize installation docs`

package/src/dew-skills/4-implementation/dew-installation-guide/steps/step-06-finalize.md

@@ -0,0 +1,19 @@
+# Step 06 — Finalize Installation Docs
+
+## Mandatory Rules
+
+- Do not finalize if install doc gate is blocked.
+- Run checklist.
+
+## Required outputs
+
+- installation-guide.md
+- usage-guide.md
+- command-reference.md
+- troubleshooting.md
+
+## Next workflow
+
+Optional:
+
+`dew-example-project`

package/src/dew-skills/4-implementation/dew-kpi-prototype/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: dew-kpi-prototype
+description: Create executable SQL, Python, or notebook prototype to compute KPI on sample data and produce validation evidence.
+---
+
+# DEW KPI Prototype
+
+**Goal:** Produce executable evidence that a KPI can be computed on sample data.
+
+**Your Role:** You are a data engineer implementing a KPI feasibility prototype.
+
+You must not create production pipeline code here. The goal is feasibility proof.
+
+## Mandatory Rules
+
+- Do not mark KPI verified unless prototype runs or user explicitly accepts caveat.
+- Do not fake sample output.
+- Do not invent fields.
+- Do not silently change KPI formula.
+- If source sample is missing, trigger `HALT-18 — No Validation Evidence`.
+- If required fields are missing, return to `dew-kpi-feasibility`.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.prototype_template}`
+   - `{workflow.sample_output_template}`
+6. Greet user in configured language.
+
+## Execution
+
+### Step 1 — Load KPI Feasibility Plan
+
+Look for:
+
+- `{planning_artifacts}/kpi-feasibility/**/sample-computation-plan.md`
+- `{planning_artifacts}/kpi-feasibility/**/kpi-feasibility-report.md`
+
+If missing, ask user to run `dew-kpi-feasibility`.
+
+### Step 2 — Select KPI
+
+Select KPI to prototype.
+
+If multiple primary KPIs exist, ask user which one to run first.
+
+### Step 3 — Locate sample data
+
+Look for:
+- `{evidence_artifacts}/source-samples/**`
+- `{evidence_artifacts}/schema-snapshots/**`
+- user-provided sample path
+- project sample data folder
+
+If missing, trigger `HALT-18`.
+
+### Step 4 — Create prototype file
+
+Create one of:
+
+- `{workflow.prototype_output_path}/{kpi_id}-prototype.sql`
+- `{workflow.prototype_output_path}/{kpi_id}-prototype.py`
+- `{workflow.prototype_output_path}/{kpi_id}-prototype.ipynb`
+- `{workflow.prototype_output_path}/{kpi_id}-manual-validation.md`
+
+Use the method specified in the computation plan.
+
+### Step 5 — Validate output
+
+Prototype must check:
+- required fields exist
+- critical fields are not unexpectedly null
+- grain is correct or intentionally transformed
+- formula is applied correctly
+- output values are plausible
+- output row count is plausible
+- caveats are documented
+
+### Step 6 — Produce evidence
+
+Create:
+
+- `{kpi_id}-sample-output.csv` or `.md`
+- `{kpi_id}-prototype-notes.md`
+
+Update evidence index.
+
+### Step 7 — Completion
+
+Do not mark KPI as verified directly.
+
+Recommend next:
+
+`dew-kpi-validation-review`

package/src/dew-skills/4-implementation/dew-kpi-prototype/assets/kpi-prototype-template.md

@@ -0,0 +1,23 @@
+# KPI Prototype Template
+
+Use this template for Python/SQL/notebook prototype notes.
+
+```markdown
+# KPI Prototype: {KPI ID} — {KPI Name}
+
+## Purpose
+
+Prove whether the KPI can be computed on sample data.
+
+## Inputs
+
+| Input | Path | Status |
+|---|---|---|
+| Source sample | | |
+| Schema snapshot | | |
+| Field mapping | | |
+
+## KPI Formula
+
+```text
+{formula}

package/src/dew-skills/4-implementation/dew-kpi-prototype/assets/kpi-sample-output-template.md

@@ -0,0 +1,40 @@
+# KPI Sample Output Template
+
+```markdown
+# KPI Sample Output: {KPI ID} — {KPI Name}
+
+## Output Summary
+
+Rows produced:
+
+Columns produced:
+
+Target grain:
+
+Observed grain:
+
+## Sample Rows
+
+| Column | Example Value | Meaning |
+|---|---|---|
+| | | |
+
+## Plausibility Review
+
+- Value range:
+- Nulls:
+- Duplicates:
+- Unexpected categories:
+- Grain issues:
+- Notes:
+
+## Caveats
+
+## Evidence Status
+
+Choose one:
+
+- valid-sample-output
+- valid-with-caveats
+- invalid
+- blocked

package/src/dew-skills/4-implementation/dew-kpi-prototype/checklist.md

@@ -0,0 +1,37 @@
+# KPI Prototype Checklist
+
+## Inputs
+
+- [ ] KPI feasibility report loaded.
+- [ ] Sample computation plan loaded.
+- [ ] KPI selected.
+- [ ] Source sample located.
+- [ ] Schema snapshot or field list located.
+
+## Prototype
+
+- [ ] Prototype file created.
+- [ ] Formula implemented as specified.
+- [ ] Required fields checked.
+- [ ] Grain checked.
+- [ ] Output generated.
+- [ ] Output saved.
+- [ ] Caveats documented.
+
+## Evidence
+
+- [ ] Prototype path recorded.
+- [ ] Sample output path recorded.
+- [ ] Validation notes created.
+- [ ] Evidence index updated.
+- [ ] Decision log updated if a decision was made.
+- [ ] Learning log updated if learning mode is enabled.
+
+## Failure conditions
+
+Fail if:
+- fields are invented
+- formula is silently changed
+- sample output is fabricated
+- output grain does not match and is not documented
+- missing evidence is ignored

package/src/dew-skills/4-implementation/dew-kpi-prototype/customize.toml

@@ -0,0 +1,27 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-kpi-prototype.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/kpi-feasibility-report.md",
+  "file:{project-root}/**/sample-computation-plan.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+prototype_template = "assets/kpi-prototype-template.md"
+sample_output_template = "assets/kpi-sample-output-template.md"
+checklist = "checklist.md"
+
+prototype_output_path = "{evidence_artifacts}/kpi-feasibility"
+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/4-implementation/dew-kpi-validation-review/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: dew-kpi-validation-review
+description: Review KPI feasibility evidence, assign feasibility status, and trigger HALT if evidence is missing.
+---
+
+# DEW KPI Validation Review
+
+**Goal:** Review KPI feasibility evidence and assign a defensible KPI status.
+
+**Your Role:** You are a data quality and feasibility reviewer.
+
+You review evidence adversarially. You do not approve KPI feasibility just because a prototype file exists.
+
+## Mandatory Rules
+
+- Do not approve KPI without evidence.
+- Do not accept sample output without checking formula, fields, grain, and caveats.
+- Do not silently ignore missing fields or grain mismatch.
+- If evidence is missing, trigger `HALT-18 — No Validation Evidence`.
+- If primary KPI remains hypothesis only, trigger `HALT-03 — KPI Feasibility Not Proven`.
+- User must approve final KPI status.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.review_template}`
+   - `{workflow.finding_rubric}`
+6. Greet user in configured language.
+
+## Execution
+
+### Step 1 — Load Evidence
+
+Load:
+- KPI feasibility report
+- field availability report
+- sample computation plan
+- prototype file
+- sample output
+- validation evidence index
+- decision log
+
+### Step 2 — Review field evidence
+
+Check:
+- required fields exist
+- field meanings are plausible
+- missing fields are documented
+- substitutes are approved
+
+### Step 3 — Review grain
+
+Check:
+- source grain
+- target KPI grain
+- aggregation/bridge logic
+- whether grain mismatch is documented
+
+### Step 4 — Review computation
+
+Check:
+- formula implemented correctly
+- filters are correct
+- aggregation is correct
+- sample output matches expected shape
+- result is plausible
+
+### Step 5 — Assign recommended status
+
+Recommend one:
+
+A. Verified on sample  
+B. Feasible with caveats  
+C. Hypothesis only  
+D. Deferred  
+E. Rejected  
+
+### Step 6 — User decision gate
+
+Ask user to approve or revise the final KPI status.
+
+Do not continue until user decides.
+
+### Step 7 — Record
+
+Update:
+- KPI feasibility report
+- validation evidence index
+- `.decision-log.md`
+- `.learning-log.md`
+
+### Step 8 — Next workflow
+
+If primary KPI is verified or caveated:
+
+Recommend:
+
+`dew-source-validation`
+
+If primary KPI is unresolved:
+
+Recommend:
+- rerun `dew-kpi-prototype`
+- revise KPI
+- defer KPI
+- reduce MVP scope

package/src/dew-skills/4-implementation/dew-kpi-validation-review/assets/kpi-validation-finding-rubric.md

@@ -0,0 +1,37 @@
+# KPI Validation Finding Rubric
+
+## High severity
+
+Use when:
+- required field is missing
+- formula cannot be implemented
+- grain is incompatible
+- sample output is invalid
+- KPI is primary and still hypothesis only
+- evidence is missing
+
+Impact:
+- blocks architecture unless user approves caveated continuation or defers KPI
+
+## Medium severity
+
+Use when:
+- field meaning is uncertain
+- sample is too small
+- source coverage is partial
+- freshness is unknown
+- output is plausible but not fully validated
+
+Impact:
+- can proceed with caveats if user approves
+
+## Low severity
+
+Use when:
+- naming issue exists
+- documentation needs clarification
+- minor caveat exists
+- evidence path needs indexing
+
+Impact:
+- does not block but must be documented

package/src/dew-skills/4-implementation/dew-kpi-validation-review/assets/kpi-validation-review-template.md

@@ -0,0 +1,98 @@
+# KPI Validation Review Template
+
+```markdown
+---
+title: "KPI Validation Review — {KPI ID}"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "4-implementation"
+relatedKPI: "{KPI ID}"
+evidence: []
+---
+
+# KPI Validation Review: {KPI ID} — {KPI Name}
+
+## 1. Review Summary
+
+Recommended status:
+
+User-approved status:
+
+## 2. Evidence Reviewed
+
+| Evidence | Path | Status | Notes |
+|---|---|---|---|
+| Feasibility report | | | |
+| Field availability | | | |
+| Sample computation plan | | | |
+| Prototype | | | |
+| Sample output | | | |
+| Evidence index | | | |
+
+## 3. Field Evidence Review
+
+| Required Field | Available? | Meaning Valid? | Notes |
+|---|---|---|---|
+| | | | |
+
+## 4. Grain Review
+
+Target grain:
+
+Observed source grain:
+
+Output grain:
+
+Finding:
+
+## 5. Formula Review
+
+Expected formula:
+
+Implemented formula:
+
+Finding:
+
+## 6. Output Plausibility Review
+
+Rows:
+
+Columns:
+
+Value ranges:
+
+Nulls:
+
+Duplicates:
+
+Unexpected values:
+
+Finding:
+
+## 7. Caveats
+
+## 8. Findings
+
+| Severity | Finding | Impact | Required Action |
+|---|---|---|---|
+| High/Medium/Low | | | |
+
+## 9. Final Status Options
+
+A. Verified on sample  
+B. Feasible with caveats  
+C. Hypothesis only  
+D. Deferred  
+E. Rejected  
+
+## 10. User Decision
+
+## 11. Downstream Impact
+
+- Architecture:
+- Source validation:
+- Transformation:
+- Serving:
+- Data quality:

package/src/dew-skills/4-implementation/dew-kpi-validation-review/checklist.md

@@ -0,0 +1,38 @@
+# KPI Validation Review Checklist
+
+## Evidence reviewed
+
+- [ ] KPI feasibility report reviewed.
+- [ ] Field availability reviewed.
+- [ ] Sample computation plan reviewed.
+- [ ] Prototype reviewed.
+- [ ] Sample output reviewed.
+- [ ] Evidence index reviewed.
+
+## Validation
+
+- [ ] Required fields checked.
+- [ ] Field meanings checked or caveated.
+- [ ] Grain compatibility checked.
+- [ ] Formula implementation checked.
+- [ ] Output plausibility checked.
+- [ ] Caveats documented.
+- [ ] Findings classified by severity.
+
+## Decision
+
+- [ ] Recommended KPI status assigned.
+- [ ] User approved final status.
+- [ ] Decision log updated.
+- [ ] Learning log updated if learning mode is enabled.
+- [ ] Evidence index updated.
+- [ ] Downstream impact documented.
+
+## Failure conditions
+
+Fail review if:
+- evidence is missing
+- formula is not implemented
+- sample output does not exist
+- required fields are missing and not caveated
+- user has not approved final status

package/src/dew-skills/4-implementation/dew-kpi-validation-review/customize.toml

@@ -0,0 +1,28 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-kpi-validation-review.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/kpi-feasibility-report.md",
+  "file:{project-root}/**/field-availability.md",
+  "file:{project-root}/**/sample-computation-plan.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+review_template = "assets/kpi-validation-review-template.md"
+finding_rubric = "assets/kpi-validation-finding-rubric.md"
+checklist = "checklist.md"
+
+review_output_path = "{evidence_artifacts}/kpi-feasibility/reviews"
+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/4-implementation/dew-learning-capture/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: dew-learning-capture
+description: Capture learning retrospective, FDE concept mapping, mistakes, decisions, and skill growth from the completed project.
+---
+
+# DEW Learning Capture
+
+**Goal:** Capture what the user learned from the project and map it to data engineering fundamentals.
+
+**Your Role:** You are a learning coach.
+
+You explain and extract lessons like a fundamental textbook, not just a project summary.
+
+## Mandatory Rules
+
+- Do not skip learning capture after release/documentation.
+- Do not write shallow lessons like “learned data engineering”.
+- Every lesson must connect to a concrete project artifact or decision.
+- Every major decision should map to a data engineering concept.
+- If learning capture is missing, trigger `HALT-19 — Learning Capture Missing`.
+
+## On Activation
+
+1. Resolve customization.
+2. Load persistent facts.
+3. Load config if present.
+4. Load:
+   - `{workflow.learning_retrospective_template}`
+   - `{workflow.fde_learning_map_template}`
+   - `{workflow.mistake_pattern_template}`
+   - `{workflow.learning_depth_rubric}`
+   - `{workflow.fde_concept_map}`
+5. Greet user in configured language.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-init.md`