dew-method 0.1.0

package/src/dew-skills/4-implementation/dew-code-review/steps/step-02-acceptance-audit.md

@@ -0,0 +1,26 @@
+# Step 02 — Acceptance Audit
+
+## Mandatory Rules
+
+- Every AC must be checked.
+- AC pass requires evidence or clear implementation proof.
+- Do not approve vague “looks done”.
+
+## Task
+
+Audit acceptance criteria.
+
+## Required table
+
+| AC | Expected | Observed | Evidence | Status |
+|---|---|---|---|---|
+
+## Update
+
+Start code review report.
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to data engineering review`

package/src/dew-skills/4-implementation/dew-code-review/steps/step-03-data-engineering-review.md

@@ -0,0 +1,31 @@
+# Step 03 — Data Engineering Review
+
+## Mandatory Rules
+
+- Review according to story layer.
+- Do not ignore grain, KPI, DQ, metadata, or operational behavior.
+
+## Review layers
+
+Run relevant layers:
+- Source/Schema Hunter
+- Grain Auditor
+- KPI Auditor
+- DQ Auditor
+- Lineage/Metadata Auditor
+- Operational Auditor
+- Caveat Auditor
+
+## Required findings
+
+Classify each finding:
+- Critical
+- High
+- Medium
+- Low
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to evidence review`

package/src/dew-skills/4-implementation/dew-code-review/steps/step-04-evidence-review.md

@@ -0,0 +1,26 @@
+# Step 04 — Evidence Review
+
+## Mandatory Rules
+
+- Required evidence must exist.
+- Evidence must match story requirement.
+- Evidence path must be recorded.
+
+## Task
+
+Review evidence manifest and files.
+
+## Required table
+
+| Evidence Requirement | Evidence Path | Present? | Valid? | Finding |
+|---|---|---|---|---|
+
+## If missing
+
+Trigger `HALT-18 — No Validation Evidence`.
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to review decision gate`

package/src/dew-skills/4-implementation/dew-code-review/steps/step-05-review-decision-gate.md

@@ -0,0 +1,36 @@
+# Step 05 — Review Decision Gate
+
+## Mandatory Rules
+
+- Stop at decision gate.
+- Reviewer decision must be explicit.
+- Critical finding blocks approval.
+
+## Decision options
+
+A. Approve  
+B. Approve with caveats  
+C. Request changes  
+D. Block  
+
+## Recommendation
+
+Recommend one option.
+
+## User/reviewer decision
+
+Ask user to choose A/B/C/D.
+
+Do not continue until user chooses.
+
+## Status impact
+
+- Approve / approve with caveats → story remains review, ready for validation
+- Request changes → story returns to in-progress
+- Block → story blocked
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize review`

package/src/dew-skills/4-implementation/dew-code-review/steps/step-06-finalize-review.md

@@ -0,0 +1,23 @@
+# Step 06 — Finalize Review
+
+## Mandatory Rules
+
+- Run checklist.
+- Update sprint status according to decision.
+- Do not mark done.
+
+## Required outputs
+
+- code review report
+- updated story review notes
+- updated sprint-status.yaml
+
+## Next workflow
+
+If approved:
+
+`dew-story-validation`
+
+If changes requested:
+
+`dew-dev-story`

package/src/dew-skills/4-implementation/dew-create-data-story/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: dew-create-data-story
+description: Create a ready-for-dev data engineering story with context, evidence requirements, acceptance criteria, tests, and Definition of Done.
+---
+
+# DEW Create Data Story
+
+**Goal:** Create one ready-for-dev data engineering story.
+
+**Your Role:** You are a story context engineer.
+
+You do not merely copy a story title from the story map. You gather all relevant design context and produce a developer-ready story.
+
+## Mandatory Rules
+
+- Create one story at a time.
+- Do not create story without sprint-status.yaml.
+- Do not create story without loading relevant design context.
+- Do not invent implementation details not supported by design.
+- Do not mark story ready-for-dev until readiness gate passes.
+- Every story must include evidence requirements.
+- Every story must include validation commands or validation approach.
+- If context is missing, mark blocked or trigger HALT-17.
+- If evidence requirements are missing, trigger HALT-18.
+
+## Workflow Architecture
+
+This workflow uses step-file architecture.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.data_story_template}`
+   - `{workflow.story_context_pack_template}`
+   - `{workflow.acceptance_criteria_rubric}`
+   - `{workflow.evidence_requirements_rubric}`
+6. Greet user in configured language.
+
+## Execution
+
+Read fully and follow:
+
+`steps/step-01-select-story.md`

package/src/dew-skills/4-implementation/dew-create-data-story/assets/data-story-template.md

@@ -0,0 +1,116 @@
+# Data Story Template
+
+```markdown
+---
+title: "{Story ID} {Story Title}"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "4-implementation"
+storyId: "{Story ID}"
+epicId: "{Epic ID}"
+storyStatus: draft
+dependsOn: []
+evidenceRequired: []
+caveats: []
+---
+
+# Story {Story ID}: {Story Title}
+
+## Status
+
+Draft / Ready for Dev / In Progress / Review / Done / Blocked
+
+## Epic
+
+{Epic ID} — {Epic Name}
+
+## Story
+
+As a data engineer,  
+I want to {implementation goal},  
+so that {data product / validation / pipeline outcome}.
+
+## Business / Data Value
+
+## Design Context
+
+### Source Context
+
+### Storage Context
+
+### Ingestion Context
+
+### Transformation Context
+
+### Model Context
+
+### DQ Context
+
+### Serving / Governance / DataOps Context
+
+## Scope
+
+### In Scope
+
+### Out of Scope
+
+## Acceptance Criteria
+
+1. Given ..., when ..., then ...
+2. Given ..., when ..., then ...
+3. Given ..., when ..., then ...
+
+## Implementation Tasks
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] Task 3
+
+## Evidence Requirements
+
+| Evidence ID | Evidence Type | Required Output | Path |
+|---|---|---|---|
+| EVD-STORY-{id}-001 | run-log | | |
+| EVD-STORY-{id}-002 | test-result | | |
+
+## Validation Commands / Approach
+
+```bash
+# command or validation approach here
+```
+
+## Data Quality Requirements
+
+| DQ Rule ID | Expected Behavior | Evidence |
+| ---------- | ----------------- | -------- |
+
+## Operational Requirements
+
+* logging:
+* error handling:
+* idempotency:
+* replay/backfill:
+* monitoring:
+
+## Files to Create / Modify
+
+| Path | Purpose |
+| ---- | ------- |
+
+## Dependencies
+
+## Caveats
+
+## Definition of Done
+
+* [ ] Implementation completed.
+* [ ] Acceptance criteria satisfied.
+* [ ] Required evidence produced.
+* [ ] DQ/test results produced.
+* [ ] File list updated.
+* [ ] Run instructions documented.
+* [ ] Story status updated to review.
+* [ ] Sprint status updated.
+```

package/src/dew-skills/4-implementation/dew-create-data-story/assets/story-acceptance-criteria-rubric.md

@@ -0,0 +1,22 @@
+# Story Acceptance Criteria Rubric
+
+Good acceptance criteria are:
+
+- specific
+- testable
+- tied to data output
+- tied to evidence
+- tied to design artifact
+- not vague
+
+## Bad
+
+- Pipeline works.
+- Data is clean.
+- Dashboard looks good.
+
+## Good
+
+- Given source sample SRC-001 exists, when ingestion runs, then a Bronze file/table is created at the target path with required metadata fields.
+- Given Bronze dataset exists, when Silver transformation runs, then required fields are cast to approved types and invalid rows are quarantined.
+- Given Gold model exists, when KPI validation runs, then KPI output matches expected grain and DQ evidence is written.

package/src/dew-skills/4-implementation/dew-create-data-story/assets/story-context-pack-template.md

@@ -0,0 +1,42 @@
+# Story Context Pack Template
+
+```markdown
+# Story Context Pack: {Story ID}
+
+## Purpose
+
+This file gathers all relevant design context for one implementation story.
+
+## Source Artifacts Used
+
+| Artifact | Path | Relevant Section |
+|---|---|---|
+
+## Extracted Context
+
+### Epic
+
+### Story Candidate
+
+### Dependencies
+
+### Relevant Source(s)
+
+### Relevant Dataset(s)
+
+### Relevant KPI(s)
+
+### Relevant DQ Rule(s)
+
+### Relevant Serving Asset(s)
+
+### Relevant Operational Requirements
+
+## Caveats
+
+## Evidence Required
+
+## Developer Notes
+
+## Open Questions
+```

package/src/dew-skills/4-implementation/dew-create-data-story/assets/story-evidence-requirements-rubric.md

@@ -0,0 +1,28 @@
+# Story Evidence Requirements Rubric
+
+Every data engineering story should produce evidence.
+
+## Common evidence types
+
+- run log
+- row count summary
+- schema snapshot
+- source access log
+- sample output
+- DQ test result
+- failed records output
+- freshness report
+- model validation report
+- metric sample output
+- screenshot/report export
+- README/run instructions
+
+## Evidence rule
+
+If a story changes data, it must produce data evidence.
+
+If a story changes a metric, it must produce metric evidence.
+
+If a story changes serving, it must produce consumer-facing evidence.
+
+If a story changes operations, it must produce runbook/monitoring evidence.

package/src/dew-skills/4-implementation/dew-create-data-story/checklist.md

@@ -0,0 +1,19 @@
+# Create Data Story Checklist
+
+- [ ] sprint-status.yaml loaded.
+- [ ] epics.md loaded.
+- [ ] story-map.md loaded.
+- [ ] Story selected.
+- [ ] Dependencies checked.
+- [ ] Relevant design artifacts loaded.
+- [ ] Story context pack created.
+- [ ] Story file created.
+- [ ] Acceptance criteria are testable.
+- [ ] Evidence requirements are explicit.
+- [ ] Validation commands/approach included.
+- [ ] DQ requirements included when relevant.
+- [ ] Operational requirements included when relevant.
+- [ ] File list included.
+- [ ] Caveats carried forward.
+- [ ] Story readiness gate approved.
+- [ ] sprint-status.yaml updated to ready-for-dev.

package/src/dew-skills/4-implementation/dew-create-data-story/customize.toml

@@ -0,0 +1,42 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-create-data-story.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/sprint-status.yaml",
+  "file:{project-root}/**/epics.md",
+  "file:{project-root}/**/story-map.md",
+  "file:{project-root}/**/data-architecture.md",
+  "file:{project-root}/**/storage-design.md",
+  "file:{project-root}/**/ingestion-design.md",
+  "file:{project-root}/**/transformation-design.md",
+  "file:{project-root}/**/data-model-spec.md",
+  "file:{project-root}/**/data-quality-rules.md",
+  "file:{project-root}/**/serving-data-product-spec.md",
+  "file:{project-root}/**/governance-security-review.md",
+  "file:{project-root}/**/dataops-runbook.md",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+data_story_template = "assets/data-story-template.md"
+story_context_pack_template = "assets/story-context-pack-template.md"
+acceptance_criteria_rubric = "assets/story-acceptance-criteria-rubric.md"
+evidence_requirements_rubric = "assets/story-evidence-requirements-rubric.md"
+checklist = "checklist.md"
+
+stories_output_path = "{implementation_artifacts}/stories"
+story_context_output_path = "{implementation_artifacts}/story-context"
+sprint_status_path = "{implementation_artifacts}/sprint/sprint-status.yaml"
+
+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-create-data-story/steps/step-01-select-story.md

@@ -0,0 +1,25 @@
+# Step 01 — Select Story
+
+## Mandatory Rules
+
+- Create one story at a time.
+- Do not create story if sprint-status.yaml is missing.
+- Respect dependency order.
+
+## Task
+
+Select next story.
+
+## Sequence
+
+1. Load `sprint-status.yaml`.
+2. Load `story-map.md`.
+3. Find first story with status `backlog` whose dependencies are done or not required.
+4. If user named a specific story, validate dependencies first.
+5. If dependencies are missing, mark blocked or recommend dependency story first.
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to load story context`

package/src/dew-skills/4-implementation/dew-create-data-story/steps/step-02-load-story-context.md

@@ -0,0 +1,74 @@
+# Step 02 — Load Story Context
+
+## Mandatory Rules
+
+- Load all design artifacts relevant to the story.
+- Do not invent missing implementation context.
+- If context is missing, trigger HALT-17.
+
+## Task
+
+Create story context pack.
+
+## Extract based on story layer
+
+### Foundation story
+
+Load:
+- data architecture
+- dataops runbook
+- governance/security
+- implementation conventions
+
+### Source access / ingestion story
+
+Load:
+- source validation
+- storage design
+- ingestion design
+- source contract tests
+- evidence index
+
+### Transformation story
+
+Load:
+- transformation design
+- data model spec
+- DQ rules
+- ingestion outputs
+
+### Gold/KPI story
+
+Load:
+- KPI feasibility
+- transformation design
+- data model spec
+- KPI-to-model mapping
+- DQ rules
+
+### Serving story
+
+Load:
+- serving design
+- metric contract
+- trust limitations
+- governance/access
+
+### DataOps story
+
+Load:
+- dataops runbook
+- observability plan
+- operational readiness report
+
+## Create
+
+Create:
+
+`{workflow.story_context_output_path}/{story_id}-context.md`
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to create story`

package/src/dew-skills/4-implementation/dew-create-data-story/steps/step-03-create-story.md

@@ -0,0 +1,44 @@
+# Step 03 — Create Story
+
+## Mandatory Rules
+
+- Story must include context, ACs, tasks, evidence, validation, DoD.
+- Do not mark ready-for-dev yet.
+- Do not omit caveats.
+
+## Task
+
+Create story file.
+
+## Create
+
+`{workflow.stories_output_path}/{story_id}-{slug}.md`
+
+Use:
+
+`{workflow.data_story_template}`
+
+## Required story sections
+
+- status
+- epic
+- story statement
+- business/data value
+- design context
+- scope
+- acceptance criteria
+- implementation tasks
+- evidence requirements
+- validation commands/approach
+- DQ requirements
+- operational requirements
+- files to create/modify
+- dependencies
+- caveats
+- Definition of Done
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to story readiness gate`

package/src/dew-skills/4-implementation/dew-create-data-story/steps/step-04-story-readiness-gate.md

@@ -0,0 +1,48 @@
+# Step 04 — Story Readiness Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- Story cannot be ready-for-dev without evidence requirements.
+- Story cannot be ready-for-dev without testable acceptance criteria.
+- User must approve or revise story readiness.
+
+## Readiness options
+
+A. Mark story ready-for-dev  
+B. Ready with caveats  
+C. Revise story  
+D. Block story  
+E. Select different story  
+
+## Required review
+
+| Area | Status | Notes |
+|---|---|---|
+| Context loaded | | |
+| Dependencies clear | | |
+| Acceptance criteria testable | | |
+| Evidence requirements explicit | | |
+| Validation approach included | | |
+| Caveats carried forward | | |
+| DoD complete | | |
+
+## User decision
+
+Ask user to choose A/B/C/D/E.
+
+Do not continue until user chooses.
+
+## Record
+
+Update:
+- story file
+- sprint-status.yaml
+- .decision-log.md if major decision
+- .learning-log.md if enabled
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize story`

package/src/dew-skills/4-implementation/dew-create-data-story/steps/step-05-finalize.md

@@ -0,0 +1,29 @@
+# Step 05 — Finalize Story
+
+## Mandatory Rules
+
+- Do not finalize as ready-for-dev unless readiness gate approved.
+- Preserve blocked/caveated status if applicable.
+- Run checklist.
+
+## Final updates
+
+If approved:
+- story frontmatter `storyStatus: ready-for-dev`
+- story status section `Ready for Dev`
+- sprint-status story status `ready-for-dev`
+
+If blocked:
+- story frontmatter `storyStatus: blocked`
+- sprint-status story status `blocked`
+- blocker documented
+
+## Next workflow
+
+Recommend:
+
+`dew-implementation-readiness-review`
+
+Or if ready:
+
+`dew-dev-story`