dew-method 0.1.0

package/src/dew-skills/4-implementation/dew-story-validation/assets/validation-evidence-rubric.md

@@ -0,0 +1,18 @@
+# Validation Evidence Rubric
+
+Evidence is valid when:
+
+- it exists at recorded path
+- it matches required evidence type
+- it was produced by this story or accepted dependency
+- it supports a specific AC/DQ/operational requirement
+- it is not only a claim in prose
+
+## Invalid evidence
+
+- missing file
+- wrong output
+- stale output
+- uncited screenshot
+- fabricated result
+- output not tied to AC

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

@@ -0,0 +1,15 @@
+# Story Validation Checklist
+
+- [ ] Story loaded.
+- [ ] Story status is review.
+- [ ] Code review loaded.
+- [ ] Review decision is approve or approve-with-caveats.
+- [ ] Dev notes loaded.
+- [ ] Evidence manifest loaded.
+- [ ] ACs validated.
+- [ ] Evidence validated.
+- [ ] DQ requirements validated if relevant.
+- [ ] Operational requirements validated if relevant.
+- [ ] Review findings resolved or caveated.
+- [ ] Done Gate approved by user.
+- [ ] Sprint status updated accordingly.

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

@@ -0,0 +1,35 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-story-validation.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/stories/**/*.md",
+  "file:{project-root}/**/story-context/**/*.md",
+  "file:{project-root}/**/dev-notes/**/*.md",
+  "file:{project-root}/**/code-review/**/*.md",
+  "file:{project-root}/**/story-evidence/**/*.md",
+  "file:{project-root}/**/sprint-status.yaml",
+  "file:{project-root}/**/validation-evidence-index.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+validation_report_template = "assets/story-validation-report-template.md"
+validation_evidence_rubric = "assets/validation-evidence-rubric.md"
+status_transition_rubric = "assets/story-status-transition-rubric.md"
+done_gate_rubric = "assets/done-gate-rubric.md"
+checklist = "checklist.md"
+
+validation_output_path = "{implementation_artifacts}/story-validation"
+sprint_status_path = "{implementation_artifacts}/sprint/sprint-status.yaml"
+evidence_index_path = "{evidence_artifacts}/validation-evidence-index.md"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-01-load-review-story-evidence.md

@@ -0,0 +1,27 @@
+# Step 01 — Load Review Story Evidence
+
+## Mandatory Rules
+
+- Validate only story status `review`.
+- Code review must be approved or approved-with-caveats.
+- Evidence manifest must exist.
+
+## Required inputs
+
+- story file
+- dev notes
+- code review report
+- evidence manifest
+- sprint-status.yaml
+
+## If missing
+
+- no review → return to `dew-code-review`
+- evidence missing → `HALT-18`
+- story not review → return to correct workflow
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to validate acceptance criteria`

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-02-validate-acceptance-criteria.md

@@ -0,0 +1,24 @@
+# Step 02 — Validate Acceptance Criteria
+
+## Mandatory Rules
+
+- Validate every AC.
+- Do not pass AC without evidence or implementation proof.
+
+## Required table
+
+| AC | Expected | Evidence | Result | Notes |
+|---|---|---|---|---|
+
+## If AC fails
+
+Recommend:
+- return to dev
+- block
+- revise story only if original AC was window and user approves
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to validate evidence`

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-03-validate-evidence.md

@@ -0,0 +1,23 @@
+# Step 03 — Validate Evidence
+
+## Mandatory Rules
+
+- Required evidence must exist and be valid.
+- Evidence must support AC/DQ/operational requirement.
+
+## Required table
+
+| Evidence ID | Required By | Path | Exists? | Valid? |
+|---|---|---|---|---|
+
+## If missing/invalid
+
+Trigger:
+
+`HALT-18 — No Validation Evidence`
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to validate DQ and operational requirements`

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-04-validate-dq-operational-requirements.md

@@ -0,0 +1,25 @@
+# Step 04 — Validate DQ and Operational Requirements
+
+## Mandatory Rules
+
+- DQ-changing story must have DQ evidence.
+- Pipeline story must have operational/logging evidence.
+- Serving story must have trust/limitations evidence.
+
+## Validate relevant areas
+
+- DQ result
+- row counts
+- schema snapshot
+- freshness report
+- run log
+- error handling
+- idempotency evidence
+- serving screenshot/API response/report
+- trust statement update
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to Done Gate`

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-05-done-gate.md

@@ -0,0 +1,31 @@
+# Step 05 — Done Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- User must approve story done.
+- Critical/high unresolved findings block done.
+- Missing evidence blocks done.
+
+## Options
+
+A. Mark done  
+B. Mark done with caveats  
+C. Return to dev  
+D. Block  
+
+## Recommendation
+
+Recommend one option.
+
+## User decision
+
+Ask user to choose A/B/C/D.
+
+Do not continue until user chooses.
+
+## Continue checkpoint
+
+Ask:
+
+`[C] Continue to finalize validation`

package/src/dew-skills/4-implementation/dew-story-validation/steps/step-06-finalize-validation.md

@@ -0,0 +1,39 @@
+# Step 06 — Finalize Validation
+
+## Mandatory Rules
+
+- Update status based on Done Gate.
+- Run checklist.
+- Do not hide caveats.
+
+## If Done / Done with caveats
+
+Update:
+- story status → Done
+- sprint-status.yaml → done
+- validation report → final
+- evidence index → validated where applicable
+
+## If Return to dev
+
+Update:
+- story status → In Progress
+- sprint-status.yaml → in-progress
+- required fixes documented
+
+## If Block
+
+Update:
+- story status → Blocked
+- sprint-status.yaml → blocked
+- blocker documented
+
+## Next workflow
+
+If done:
+
+`dew-story-completion`
+
+If not done:
+
+`dew-dev-story`

package/src/dew-skills/module-help.csv

@@ -0,0 +1,46 @@
+module,skill,display-name,menu-code,description,action,args,phase,preceded-by,followed-by,required,output-location,outputs
+DEW,_meta,,,,,,,,,false,,
+DEW,dew-decision-gate,Decision Gate,DG,Run a mandatory project-shaping decision gate with evidence options trade-offs and user approval.,,,1-analysis,,,true,planning_artifacts,decision gate result
+DEW,dew-halt-resolver,Halt Resolver,HR,Resolve a DEW HALT by explaining risk options evidence requirements and resume conditions.,,,1-analysis,,,true,planning_artifacts,halt resolution
+DEW,dew-evidence-check,Evidence Check,EC,Check whether a phase has required validation evidence before it can be marked done.,,,1-analysis,,,true,evidence_artifacts,evidence check report
+DEW,dew-project-brief,Project Brief,PB,Create update or validate a DEW project brief focused on data engineering scope business purpose and learning objective.,,,1-analysis,,,true,planning_artifacts,project brief
+DEW,dew-business-discovery,Business Discovery,BD,Clarify business decision data consumers stakeholders and decision context before KPI/source work.,,,1-analysis,dew-project-brief,dew-kpi-discovery,true,planning_artifacts,business discovery
+DEW,dew-kpi-discovery,KPI Discovery,KD,Define candidate KPIs formulas grains required fields and source dependencies without claiming feasibility.,,,1-analysis,dew-business-discovery,dew-data-product-prd,true,planning_artifacts,kpi catalog
+DEW,dew-data-product-prd,Data Product PRD,DPRD,Create update or validate a data product PRD with consumers KPIs grain freshness trust expectations and caveats.,,,2-plan-workflows,dew-kpi-discovery,,true,planning_artifacts,data product PRD
+DEW,dew-kpi-feasibility,KPI Feasibility,KF,Validate whether candidate KPIs can be computed from available fields samples and source evidence before architecture.,,,2-plan-workflows,dew-data-product-prd,dew-kpi-prototype,true,planning_artifacts,kpi feasibility report
+DEW,dew-kpi-prototype,KPI Prototype,KP,Create executable SQL Python or notebook prototype to compute KPI on sample data and produce evidence.,,,4-implementation,dew-kpi-feasibility,dew-kpi-validation-review,true,evidence_artifacts,kpi prototype and sample output
+DEW,dew-kpi-validation-review,KPI Validation Review,KVR,Review KPI feasibility evidence assign feasibility status and trigger HALT if evidence is missing.,,,4-implementation,dew-kpi-prototype,,true,evidence_artifacts,kpi validation review
+DEW,dew-source-discovery,Source Discovery,SD,Discover candidate data sources and document their expected role access method owner grain and source type without accepting them yet.,,,2-plan-workflows,dew-data-product-prd,dew-source-assessment,true,planning_artifacts,source inventory
+DEW,dew-source-assessment,Source Assessment,SA,Assess candidate sources for relevance risk field coverage ownership grain freshness and validation priority.,,,2-plan-workflows,dew-source-discovery,dew-source-validation,true,planning_artifacts,source scorecard
+DEW,dew-source-validation,Source Validation,SV,Validate source access sample schema grain freshness quality and trust before promoting sources to P1.,,,2-plan-workflows,dew-source-assessment,dew-source-access-check,true,planning_artifacts,source validation report
+DEW,dew-source-access-check,Source Access Check,SAC,Run or document source access checks such as API call file download database query or manual acquisition.,,,4-implementation,dew-source-validation,dew-source-sampler,true,evidence_artifacts,source access evidence
+DEW,dew-source-sampler,Source Sampler,SSM,Extract or document source samples and schema snapshots as evidence for source validation.,,,4-implementation,dew-source-access-check,dew-source-contract-test,true,evidence_artifacts,source sample and schema snapshot
+DEW,dew-source-contract-test,Source Contract Test,SCT,Define and run minimal source contract tests for schema required fields freshness and grain expectations.,,,4-implementation,dew-source-sampler,,true,evidence_artifacts,source contract test
+DEW,dew-requirement-gate,Requirement Gate,RG,Review KPI feasibility source validation trust grain freshness caveats and MVP scope before allowing architecture.,,,2-plan-workflows,dew-source-validation,dew-data-architecture,true,planning_artifacts,requirement gate report
+DEW,dew-data-architecture,Data Architecture,DA,Create evidence-grounded data architecture from requirement gate KPI feasibility source validation and approved caveats.,,,3-solutioning,dew-requirement-gate,dew-storage-design,true,planning_artifacts,data architecture
+DEW,dew-storage-design,Storage Design,STG,Design storage layers raw bronze silver gold metadata retention schema snapshot and source-to-storage mapping from approved architecture.,,,3-solutioning,dew-data-architecture,dew-ingestion-design,true,planning_artifacts,storage design
+DEW,dew-ingestion-design,Ingestion Design,ING,Design ingestion patterns source extraction frequency schema evolution failure handling idempotency replay and evidence requirements.,,,3-solutioning,dew-storage-design,dew-transformation-design,true,planning_artifacts,ingestion design
+DEW,dew-transformation-design,Transformation Design,TR,Design Bronze to Silver and Silver to Gold transformation rules grain changes business rules and caveat carryover.,,,3-solutioning,dew-ingestion-design,dew-data-model-design,true,planning_artifacts,transformation design
+DEW,dew-data-model-design,Data Model Design,DM,Design Silver and Gold data models with explicit grain KPI mapping bridge tables dimensions facts and history handling.,,,3-solutioning,dew-transformation-design,dew-data-quality-design,true,planning_artifacts,data model spec
+DEW,dew-data-quality-design,Data Quality Design,DQ,Define data quality rules severity actions evidence requirements and test handoff for source transformation and serving layers.,,,3-solutioning,dew-data-model-design,dew-serving-design,true,planning_artifacts,data quality rules
+DEW,dew-serving-design,Serving Design,SRV,Design how Gold models metrics and data products are served to consumers with trust caveats contracts and feedback loop.,,,3-solutioning,dew-data-quality-design,dew-governance-security-design,true,planning_artifacts,serving data product spec
+DEW,dew-governance-security-design,Governance Security Design,GOV,Design privacy posture access control ownership lineage metadata auditability and governance rules for the data product.,,,3-solutioning,dew-serving-design,dew-dataops-design,true,planning_artifacts,governance security review
+DEW,dew-dataops-design,DataOps Design,DOPS,Design operational readiness monitoring alerting incident handling backfill change process environments and CI CD handoff.,,,3-solutioning,dew-governance-security-design,dew-create-epics-and-stories,true,planning_artifacts,dataops runbook
+DEW,dew-create-epics-and-stories,Create Epics and Stories,CES,Convert approved DEW designs into data engineering epics story map dependencies and implementation backlog.,,,3-solutioning,dew-dataops-design,dew-sprint-planning,true,planning_artifacts,epics and story map
+DEW,dew-sprint-planning,Sprint Planning,SP,Create sprint-status.yaml and plan implementation order for DEW epics and stories.,,,4-implementation,dew-create-epics-and-stories,dew-create-data-story,true,implementation_artifacts,sprint status
+DEW,dew-create-data-story,Create Data Story,CDS,Create a ready-for-dev data engineering story with context evidence requirements acceptance criteria tests and DoD.,,,4-implementation,dew-sprint-planning,dew-implementation-readiness-review,true,implementation_artifacts,data story
+DEW,dew-implementation-readiness-review,Implementation Readiness Review,IRR,Review whether generated stories have enough context evidence criteria dependencies and DoD before development starts.,,,4-implementation,dew-create-data-story,dew-dev-story,true,implementation_artifacts,implementation readiness report
+DEW,dew-dev-story,Dev Story,DEV,Implement a ready-for-dev data engineering story while producing required evidence logs tests and story updates.,,,4-implementation,dew-implementation-readiness-review,dew-code-review,true,implementation_artifacts,implemented story evidence
+DEW,dew-code-review,Code Review,CR,Review implemented data engineering story for AC compliance DQ evidence grain lineage operational behavior and caveats.,,,4-implementation,dew-dev-story,dew-story-validation,true,implementation_artifacts,code review report
+DEW,dew-story-validation,Story Validation,SVL,Validate acceptance criteria evidence DQ operational requirements and decide whether story can move to done.,,,4-implementation,dew-code-review,dew-story-completion,true,implementation_artifacts,story validation report
+DEW,dew-story-completion,Story Completion,SC,Finalize story completion notes learning capture file list evidence index and sprint status after validation passes.,,,4-implementation,dew-story-validation,,true,implementation_artifacts,story completion
+DEW,dew-e2e-validation,E2E Validation,E2E,Validate the implemented data product from source through storage ingestion transformation DQ Gold and serving outputs.,,,4-implementation,dew-story-completion,dew-final-evidence-review,true,implementation_artifacts,e2e validation report
+DEW,dew-final-evidence-review,Final Evidence Review,FER,Review whether all required implementation validation DQ serving governance and operational evidence exists before release.,,,4-implementation,dew-e2e-validation,dew-release-readiness,true,implementation_artifacts,final evidence review
+DEW,dew-release-readiness,Release Readiness,RR,Decide whether the data product is ready to release with scope caveats risks notes and rollback guidance.,,,4-implementation,dew-final-evidence-review,dew-project-documentation,true,implementation_artifacts,release readiness report
+DEW,dew-project-documentation,Project Documentation,DOC,Create user-facing and technical documentation for the released data product from validated artifacts evidence and release notes.,,,4-implementation,dew-release-readiness,dew-learning-capture,true,implementation_artifacts,project documentation
+DEW,dew-learning-capture,Learning Capture,LC,Capture learning retrospective FDE concept mapping mistakes decisions and skill growth from the completed project.,,,4-implementation,dew-project-documentation,dew-pattern-extraction,true,learning_artifacts,learning retrospective
+DEW,dew-pattern-extraction,Pattern Extraction,PEX,Extract reusable data engineering patterns anti-patterns and templates from the completed DEW project.,,,4-implementation,dew-learning-capture,dew-skill-qa,true,learning_artifacts,reusable patterns
+DEW,dew-skill-qa,Skill QA,SQA,Audit DEW skill pack structure module catalog cross-links gates HALTs assets steps and checklist consistency before release.,,,4-implementation,dew-pattern-extraction,dew-package-release,true,implementation_artifacts,skill qa report
+DEW,dew-package-release,Package Release,PKG,Package the DEW skill module for release with versioning release notes checklist and package readiness gate.,,,4-implementation,dew-skill-qa,dew-installation-guide,true,implementation_artifacts,package release report
+DEW,dew-installation-guide,Installation Guide,INSTALL,Create installation usage command reference and troubleshooting documentation for the DEW skill module.,,,4-implementation,dew-package-release,dew-example-project,true,implementation_artifacts,installation guide
+DEW,dew-example-project,Example Project,EX,Create a quickstart example project walkthrough showing how to use DEW from brief to release.,,,4-implementation,dew-installation-guide,,false,implementation_artifacts,example project walkthrough

package/src/dew-skills/module.yaml

@@ -0,0 +1,118 @@
+code: dew
+name: "Data Engineering Workflow"
+version: "1.0.0"
+description: "Evidence-driven data engineering workflow based on Fundamentals of Data Engineering and BMAD-style phased skills."
+default_selected: true
+requires:
+  - core
+
+# Variables from Core Config inserted:
+## user_name
+## project_name
+## communication_language
+## document_output_language
+## output_folder
+
+user_skill_level:
+  prompt:
+    - "What is your data engineering experience level?"
+    - "This affects how agents explain concepts in chat."
+  scope: user
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - Explain fundamentals carefully"
+    - value: "intermediate"
+      label: "Intermediate - Balance detail with speed"
+    - value: "expert"
+      label: "Expert - Be direct and technical"
+
+learning_mode:
+  prompt:
+    - "Should DEW explain concepts and trade-offs at decision gates?"
+  scope: user
+  default: "true"
+  result: "{value}"
+
+planning_artifacts:
+  prompt: "Where should planning artifacts be stored?"
+  default: "{output_folder}/planning-artifacts"
+  result: "{project-root}/{value}"
+
+implementation_artifacts:
+  prompt: "Where should implementation artifacts be stored?"
+  default: "{output_folder}/implementation-artifacts"
+  result: "{project-root}/{value}"
+
+project_knowledge:
+  prompt: "Where should long-term project knowledge be stored?"
+  default: "docs"
+  result: "{project-root}/{value}"
+
+evidence_artifacts:
+  prompt: "Where should validation evidence be stored?"
+  default: "{output_folder}/evidence-artifacts"
+  result: "{project-root}/{value}"
+
+learning_artifacts:
+  prompt: "Where should learning notes be stored?"
+  default: "{output_folder}/learning-artifacts"
+  result: "{project-root}/{value}"
+
+directories:
+  - "{planning_artifacts}"
+  - "{implementation_artifacts}"
+  - "{project_knowledge}"
+  - "{evidence_artifacts}"
+  - "{learning_artifacts}"
+
+agents:
+  - code: dew-agent-data-analyst
+    name: Linh
+    title: Data Analyst
+    icon: "📊"
+    team: data-engineering
+    description: "Clarifies business questions, KPI definitions, data consumers, and decision context."
+
+  - code: dew-agent-source-validator
+    name: Quang
+    title: Source Validation Engineer
+    icon: "🔎"
+    team: data-engineering
+    description: "Validates source access, schema, samples, freshness, quality, and feasibility before architecture."
+
+  - code: dew-agent-data-architect
+    name: An
+    title: Data Architect
+    icon: "🏗️"
+    team: data-engineering
+    description: "Designs lifecycle architecture, storage, ingestion, transformation, serving, and trade-offs."
+
+  - code: dew-agent-data-engineer
+    name: Khoa
+    title: Data Engineer
+    icon: "💻"
+    team: data-engineering
+    description: "Implements ingestion, transformations, orchestration, tests, and pipeline logic."
+
+  - code: dew-agent-data-quality-engineer
+    name: Nhi
+    title: Data Quality Engineer
+    icon: "🧪"
+    team: data-engineering
+    description: "Defines and validates data quality rules, contract tests, profiling, and evidence."
+
+  - code: dew-agent-governance-specialist
+    name: Trang
+    title: Data Governance Specialist
+    icon: "🔐"
+    team: data-engineering
+    description: "Reviews privacy, access control, lineage, metadata, auditability, and compliance posture."
+
+  - code: dew-agent-technical-writer
+    name: Paige
+    title: Technical Writer
+    icon: "📚"
+    team: data-engineering
+    description: "Creates clear documentation, diagrams, learning notes, and reusable patterns."

package/tools/installer/dew-cli.js

@@ -0,0 +1,50 @@
+#!/usr/bin/env node
+
+const { program } = require('commander');
+const { installDew } = require('./install');
+const { listModules } = require('./list');
+const { validatePackage } = require('./validate');
+const packageJson = require('../../package.json');
+
+program
+  .name('dew')
+  .description('DEW CLI - Data Engineering Workflow installer')
+  .version(packageJson.version);
+
+program
+  .command('install')
+  .description('Install DEW runtime, modules, output folders, and agent skills into a project')
+  .option('-d, --directory <path>', 'Installation directory', process.cwd())
+  .option('-y, --yes', 'Accept defaults and run non-interactively')
+  .option('--user-name <name>', 'Name for DEW agents to use')
+  .option('--project-name <name>', 'Project name')
+  .option('--communication-language <lang>', 'Language for agent communication')
+  .option('--document-output-language <lang>', 'Language for document output')
+  .option('--output-folder <path>', 'Output folder path relative to project root', '_dew-output')
+  .action((options) => {
+    installDew(options).catch((error) => {
+      console.error(`DEW installation failed: ${error.message}`);
+      if (error.stack) console.error(error.stack);
+      process.exit(1);
+    });
+  });
+
+program
+  .command('list')
+  .description('List bundled DEW modules and skill catalogs')
+  .action(() => {
+    listModules();
+  });
+
+program
+  .command('validate')
+  .description('Validate package runtime files before publishing')
+  .action(() => {
+    validatePackage();
+  });
+
+program.parse(process.argv);
+
+if (process.argv.slice(2).length === 0) {
+  program.outputHelp();
+}