dew-method 0.1.0

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-02-load-validated-context.md

@@ -0,0 +1,70 @@
+# Step 02 — Load Validated Context
+
+## Mandatory Rules
+
+- Load all prior validated artifacts before judging readiness.
+- Do not treat missing artifacts as completed.
+- Do not treat caveats as evidence.
+- If KPI feasibility report is missing, trigger `HALT-03`.
+- If source validation report is missing, trigger `HALT-06` or `HALT-18`.
+
+## Task
+
+Load and summarize all required prior artifacts.
+
+## Input discovery
+
+Search for:
+
+- `{planning_artifacts}/**/brief.md`
+- `{planning_artifacts}/**/business-discovery.md`
+- `{planning_artifacts}/**/data-product-prd.md`
+- `{planning_artifacts}/**/kpi-catalog.md`
+- `{planning_artifacts}/**/kpi-source-matrix.md`
+- `{planning_artifacts}/**/kpi-feasibility-report.md`
+- `{planning_artifacts}/**/source-inventory.md`
+- `{planning_artifacts}/**/source-scorecard.md`
+- `{planning_artifacts}/**/source-validation-report.md`
+- `{evidence_artifacts}/**/validation-evidence-index.md`
+- `{planning_artifacts}/**/.decision-log.md`
+- `{learning_artifacts}/**/.learning-log.md`
+
+## Extract
+
+Extract:
+
+### Business
+- data consumer
+- decision supported
+- data product type
+- MVP scope
+
+### KPI
+- primary KPI list
+- feasibility status
+- unresolved KPI blockers
+- KPI caveats
+
+### Source
+- validation-first source list
+- P1/P2/exploration/rejected/block status
+- source evidence
+- unresolved source blockers
+- source caveats
+
+### Evidence
+- KPI evidence
+- source evidence
+- missing evidence
+- stale/invalid evidence if any
+
+## Update report
+
+Append input artifact table and executive readiness summary.
+
+Update frontmatter:
+
+```yaml
+stepsCompleted:
+  - step-01-init
+  - step-02-load-validated-context

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-03-kpi-readiness-review.md

@@ -0,0 +1,85 @@
+# Step 03 — KPI Readiness Review
+
+## Mandatory Rules
+
+- Do not mark a KPI ready without feasibility status.
+- Primary KPI cannot remain `Hypothesis only` unless user explicitly accepts caveated continuation or defers it.
+- Missing KPI evidence must trigger `HALT-03` or `HALT-18`.
+
+## Task
+
+Review whether KPI requirements are ready for architecture.
+
+## For each primary KPI
+
+Review:
+
+| KPI ID | KPI Name | Feasibility Status | Evidence | Caveat | Architecture Impact |
+|---|---|---|---|---|---|
+
+## Allowed KPI readiness statuses
+
+- Ready
+- Ready with caveats
+- Blocked
+- Deferred
+- Rejected
+
+## Decision cases
+
+### Ready
+
+Use when:
+- KPI is verified on sample
+- or feasible with caveats approved
+
+### Ready with caveats
+
+Use when:
+- sample validation exists but limitations remain
+- user accepts caveats
+- downstream impact is clear
+
+### Blocked
+
+Use when:
+- KPI is hypothesis only
+- required fields unresolved
+- formula/grain unclear
+- sample computation missing
+
+### Deferred
+
+Use when:
+- KPI removed from MVP by user decision
+
+### Rejected
+
+Use when:
+- KPI is invalid or not feasible
+
+## If primary KPI is blocked
+
+Trigger:
+
+`HALT-03 — KPI Feasibility Not Proven`
+
+Options:
+A. Return to KPI feasibility  
+B. Continue with caveat  
+C. Defer KPI  
+D. Reduce MVP scope  
+
+## Update report
+
+Update KPI Readiness section.
+
+Update caveat register if caveats exist.
+
+Update frontmatter:
+
+```yaml
+stepsCompleted:
+  - step-01-init
+  - step-02-load-validated-context
+  - step-03-kpi-readiness-review

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-04-source-readiness-review.md

@@ -0,0 +1,66 @@
+# Step 04 — Source Readiness Review
+
+## Mandatory Rules
+
+- Do not mark a source ready without validation status.
+- Do not treat candidate source as P1.
+- P1 source cannot lack access/sample/schema evidence unless user explicitly accepts caveat.
+- Missing source evidence triggers `HALT-06` or `HALT-18`.
+
+## Task
+
+Review whether source requirements are ready for architecture.
+
+## For each source needed by MVP
+
+Review:
+
+| Source ID | Source Name | Validation Status | Evidence | Caveat | Architecture Impact |
+|---|---|---|---|---|---|
+
+## Required source evidence for P1
+
+- access check
+- sample
+- schema snapshot
+- grain assessment
+- freshness assessment
+- field coverage
+- DQ/profile notes or caveat
+- source trust decision
+
+## Allowed source readiness statuses
+
+- Ready
+- Ready with caveats
+- Blocked
+- Deferred
+- Rejected
+- Exploration only
+
+## If P1 source is blocked
+
+Trigger:
+
+`HALT-06 — Source Trust Not Established`
+
+Options:
+A. Return to source validation  
+B. Continue with caveat  
+C. Defer source  
+D. Reduce MVP scope  
+
+## Update report
+
+Update Source Readiness section.
+
+Update caveat register if caveats exist.
+
+Update frontmatter:
+
+```yaml
+stepsCompleted:
+  - step-01-init
+  - step-02-load-validated-context
+  - step-03-kpi-readiness-review
+  - step-04-source-readiness-review

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-05-trust-grain-freshness-gates.md

@@ -0,0 +1,45 @@
+# Step 05 — Trust, Grain, and Freshness Gates
+
+## Mandatory Rules
+
+- Stop for user decisions.
+- Trust expectation must be explicitly selected.
+- Grain must be approved or caveated.
+- Freshness must be approved or caveated.
+- Do not proceed to architecture readiness gate until these gates are resolved.
+
+## Task
+
+Resolve three core readiness gates:
+
+1. Trust Expectation Gate
+2. Grain Gate
+3. Freshness Gate
+
+---
+
+## Gate 1 — Trust Expectation
+
+Explain:
+
+Trust expectation defines how much confidence downstream consumers can place in the data product.
+
+Options:
+
+A. Exploratory only  
+B. Internal decision-support with documented limitations  
+C. Trusted shared product with quality checks  
+D. Production-grade with contracts and monitoring  
+
+Recommend based on current artifacts.
+
+Ask user to choose.
+
+Do not continue until user chooses.
+
+Update:
+
+```yaml
+decisionGates:
+  GATE-05-trust-expectation:
+    status: approved / approved-with-caveats

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-06-scope-caveat-resolution.md

@@ -0,0 +1,75 @@
+# Step 06 — Scope and Caveat Resolution
+
+## Mandatory Rules
+
+- Caveats must be explicit.
+- High severity caveats must be accepted by the user or block the gate.
+- User-approved caveats are not evidence.
+- Every caveat needs downstream impact and revisit trigger.
+
+## Task
+
+Resolve caveats and MVP scope before architecture.
+
+## Build Caveat Register
+
+For each caveat, capture:
+
+| Caveat ID | Area | Description | Severity | Accepted? | Downstream Impact | Revisit Trigger |
+|---|---|---|---|---|---|---|
+
+## Severity
+
+### High
+
+Blocks architecture unless accepted explicitly.
+
+Examples:
+- primary KPI not sample-verified
+- P1 source lacks schema evidence
+- source grain unknown
+- freshness unknown for decision-critical output
+- privacy/security unresolved
+
+### Medium
+
+Can proceed with caveat if documented.
+
+Examples:
+- limited sample size
+- field meaning needs owner confirmation
+- source update pattern not formally guaranteed
+
+### Low
+
+Documentation or minor uncertainty.
+
+## Scope options
+
+If caveats are too severe, present options:
+
+A. Keep current MVP with caveats  
+B. Reduce MVP scope  
+C. Defer unresolved KPI/source  
+D. Return to validation  
+E. Stop architecture readiness  
+
+Ask user to choose if any High caveat exists.
+
+## Update report
+
+Update:
+- Caveat Register
+- MVP scope impact
+- Architecture readiness matrix
+
+Update frontmatter:
+
+```yaml
+stepsCompleted:
+  - step-01-init
+  - step-02-load-validated-context
+  - step-03-kpi-readiness-review
+  - step-04-source-readiness-review
+  - step-05-trust-grain-freshness-gates
+  - step-06-scope-caveat-resolution

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-07-architecture-readiness-gate.md

@@ -0,0 +1,63 @@
+# Step 07 — Architecture Readiness Gate
+
+## Mandatory Rules
+
+- Stop at this gate.
+- Recommend, but do not decide.
+- User must explicitly approve architecture readiness.
+- Do not approve if hard blockers remain.
+- If architecture is not ready, recommend exact workflow to return to.
+
+## Task
+
+Run GATE-12 — Architecture Readiness Gate.
+
+## Required readiness matrix
+
+Complete:
+
+| Requirement | Status | Evidence | Decision |
+|---|---|---|---|
+| Business decision clear | | | |
+| Data consumer clear | | | |
+| Primary KPI feasible or caveated | | | |
+| P1 source validated or caveated | | | |
+| Trust expectation approved | | | |
+| Grain approved | | | |
+| Freshness approved | | | |
+| Schema evolution direction known | | | |
+| Caveats accepted | | | |
+| Evidence indexed | | | |
+
+## Final decision options
+
+A. Proceed to architecture  
+B. Proceed to architecture with caveats  
+C. Return to KPI validation  
+D. Return to source validation  
+E. Reduce MVP scope  
+
+## Recommendation
+
+Recommend one option based on readiness matrix.
+
+## User decision
+
+Ask user to choose A/B/C/D/E.
+
+Do not continue until user chooses.
+
+## Record decision
+
+Update `.decision-log.md`.
+
+If learning mode is enabled, update `.learning-log.md`.
+
+Update frontmatter:
+
+```yaml
+decisionGates:
+  GATE-12-architecture-readiness:
+    status: approved / approved-with-caveats / blocked
+architectureReadiness:
+  status: ready / ready-with-caveats / blocked / scope-reduction-needed

package/src/dew-skills/2-plan-workflows/dew-requirement-gate/steps/step-08-finalize.md

@@ -0,0 +1,43 @@
+# Step 08 — Finalize Requirement Gate Report
+
+## Mandatory Rules
+
+- Do not finalize as ready if architecture readiness gate is blocked.
+- Do not hide unresolved blockers.
+- Do not remove caveats from the report.
+- Evidence index must be referenced.
+
+## Task
+
+Finalize requirement gate report.
+
+## Run checklist
+
+Use:
+
+`{workflow.checklist}`
+
+## Required outputs
+
+- `requirement-gate-report.md`
+- `caveat-register.md`
+- `architecture-readiness-matrix.md`
+- decision log entry
+- learning log entry if enabled
+
+## Final report status
+
+Set:
+
+```yaml
+status: final
+updated: {date}
+stepsCompleted:
+  - step-01-init
+  - step-02-load-validated-context
+  - step-03-kpi-readiness-review
+  - step-04-source-readiness-review
+  - step-05-trust-grain-freshness-gates
+  - step-06-scope-caveat-resolution
+  - step-07-architecture-readiness-gate
+  - step-08-finalize

package/src/dew-skills/2-plan-workflows/dew-source-assessment/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: dew-source-assessment
+description: Assess candidate sources for relevance, risk, field coverage, ownership, grain, freshness, and validation priority.
+---
+
+# DEW Source Assessment
+
+**Goal:** Prioritize candidate sources for validation and identify risks before running technical source validation.
+
+**Your Role:** You are a source assessment facilitator.
+
+You assess candidate sources, but you must not accept them as P1 without validation evidence.
+
+## Mandatory Rules
+
+- Do not promote source to P1 without validation evidence.
+- Do not assume access works.
+- Do not assume schema is stable.
+- Do not assume source grain matches KPI grain.
+- Do not hide source caveats.
+- If source trust is unclear, trigger `HALT-06 — Source Trust Not Established`.
+
+## On Activation
+
+1. Resolve customization.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config if present.
+5. Load:
+   - `{workflow.source_scorecard_template}`
+   - `{workflow.source_risk_rubric}`
+   - `{workflow.source_priority_rubric}`
+6. Greet user in configured language.
+
+## Execution
+
+### Step 1 — Load Source Inventory
+
+Look for:
+- `{planning_artifacts}/source-discovery/**/source-inventory.md`
+- `{planning_artifacts}/**/*source*inventory*.md`
+
+If missing, ask user to run `dew-source-discovery`.
+
+### Step 2 — Load KPI Context
+
+Look for:
+- KPI catalog
+- KPI-source matrix
+- data product PRD
+- KPI feasibility report if available
+
+### Step 3 — Score each source
+
+Assess:
+- KPI relevance
+- access risk
+- ownership/provider clarity
+- expected field coverage
+- expected grain compatibility
+- expected freshness
+- schema stability risk
+- privacy/security risk
+- license/terms risk
+- operational reliability
+- validation effort
+
+### Step 4 — Assign validation priority
+
+Priority values:
+
+- Validate first
+- Validate later
+- Exploration only
+- Reject early
+- Blocked
+
+### Step 5 — Create Source Scorecard
+
+Create:
+
+`{workflow.assessment_output_path}/{workflow.run_folder_pattern}/source-scorecard.md`
+
+### Step 6 — Finalize
+
+Run checklist.
+
+Recommend next:
+
+`dew-source-validation`

package/src/dew-skills/2-plan-workflows/dew-source-assessment/assets/source-priority-rubric.md

@@ -0,0 +1,36 @@
+# Source Priority Rubric
+
+## Validate first
+
+Use when:
+- source supports primary KPI
+- source is likely essential for MVP
+- source risk must be resolved before architecture
+
+## Validate later
+
+Use when:
+- source supports secondary KPI
+- source useful but not MVP-critical
+- source can be deferred without blocking architecture
+
+## Exploration only
+
+Use when:
+- source may be useful for learning
+- source is not reliable enough yet
+- source is not required for MVP
+
+## Reject early
+
+Use when:
+- source does not support KPI/product needs
+- source is clearly inaccessible
+- license or privacy risk is unacceptable
+- better source exists
+
+## Blocked
+
+Use when:
+- source is likely important
+- but access/owner/legal/technical constraints block validation

package/src/dew-skills/2-plan-workflows/dew-source-assessment/assets/source-risk-rubric.md

@@ -0,0 +1,70 @@
+# Source Risk Rubric
+
+## Access Risk
+
+High when:
+- authentication unknown
+- source may be blocked
+- manual access only
+- rate limit or licensing unclear
+
+Medium when:
+- access method known but untested
+
+Low when:
+- access method is simple and likely testable
+
+## Field Coverage Risk
+
+High when:
+- required KPI fields are not clearly present
+
+Medium when:
+- fields may exist but names/meaning are uncertain
+
+Low when:
+- fields are documented and map cleanly to KPI needs
+
+## Grain Risk
+
+High when:
+- source grain is unknown or likely incompatible
+
+Medium when:
+- source requires aggregation, bridge, or mapping
+
+Low when:
+- source grain matches KPI/product grain
+
+## Freshness Risk
+
+High when:
+- update frequency is unknown or slower than product requirement
+
+Medium when:
+- likely sufficient but not verified
+
+Low when:
+- source update pattern is documented and fits requirement
+
+## Schema Stability Risk
+
+High when:
+- no contract, docs, versioning, or stable structure
+
+Medium when:
+- schema stable historically but no formal contract
+
+Low when:
+- schema is documented/versioned/contracted
+
+## Privacy/Security Risk
+
+High when:
+- PII/sensitive/regulated data may exist
+
+Medium when:
+- internal or restricted data exists
+
+Low when:
+- public non-sensitive data