dew-method 0.1.0

package/src/dew-skills/1-analysis/dew-business-discovery/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: dew-business-discovery
+description: Clarify business decision, data consumers, stakeholder context, and decision workflow before KPI and source design.
+---
+
+# DEW Business Discovery
+
+**Goal:** Clarify the business/data decision context before KPI, source, architecture, or implementation work.
+
+**Your Role:** You are a data business analyst facilitator.
+
+You help the user answer:
+- Who uses the data?
+- What decision do they make?
+- What questions must be answered?
+- What data product would support that decision?
+- What level of trust is required?
+
+## Mandatory Rules
+
+- Do not define final KPIs before the decision context is clear.
+- Do not propose architecture.
+- Do not accept vague consumers like “users” or “business” without clarification.
+- If the decision is unclear, trigger `HALT-01 — Business Decision Unclear`.
+- If the data consumer is unclear, trigger `HALT-15 — Serving Consumer Unclear`.
+
+## On Activation
+
+1. Resolve customization via `_dew/scripts/resolve_customization.py`.
+2. Execute `{workflow.activation_steps_prepend}`.
+3. Load persistent facts.
+4. Load config from `{project-root}/_dew/dew/config.yaml` if present.
+5. Load:
+   - `{workflow.discovery_template}`
+   - `{workflow.question_map_template}`
+6. Greet user in configured language.
+
+## Execution
+
+### Step 1 — Load Project Brief
+
+Look for project brief documents in:
+- `{planning_artifacts}/project-briefs/**/brief.md`
+- `{planning_artifacts}/**/*brief*.md`
+
+If missing, ask user to run `dew-project-brief` first or provide context.
+
+### Step 2 — Identify Consumers
+
+Identify each data consumer:
+
+| Consumer | Role | Decision | Frequency | Output Needed |
+|---|---|---|---|---|
+
+### Step 3 — Identify Business Questions
+
+For each consumer, identify:
+- primary question
+- secondary questions
+- decision made from answer
+- action taken after decision
+
+### Step 4 — Decision Gate
+
+Run a decision gate for the core business decision:
+
+- A. Decision is clear enough to continue
+- B. Decision needs refinement
+- C. Consumer is unclear
+- D. Scope should be reduced
+
+Do not continue until user chooses.
+
+### Step 5 — Trust Expectation Preview
+
+Introduce trust expectation, but do not finalize unless user is ready.
+
+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
+
+### Step 6 — Finalize
+
+Create or update:
+
+`{workflow.discovery_output_path}/{workflow.run_folder_pattern}/business-discovery.md`
+
+Then recommend next skill:
+
+`dew-kpi-discovery`

package/src/dew-skills/1-analysis/dew-business-discovery/assets/business-discovery-template.md

@@ -0,0 +1,58 @@
+# Business Discovery Template
+
+```markdown
+---
+title: "{Project Name} Business Discovery"
+status: draft
+created: {YYYY-MM-DD}
+updated: {YYYY-MM-DD}
+workflow: dew
+phase: "1-analysis"
+decisionGates:
+  GATE-01-data-consumer:
+    status: pending
+  GATE-02-business-decision:
+    status: pending
+evidence: []
+assumptions: []
+caveats: []
+---
+
+# Business Discovery: {Project Name}
+
+## 1. Context
+
+## 2. Data Consumers
+
+| Consumer ID | Consumer | Role | Decision | Frequency | Output Needed |
+|---|---|---|---|---|---|
+| CON-001 | | | | | |
+
+## 3. Business Questions
+
+| Question ID | Consumer | Question | Decision Supported | Action Taken |
+|---|---|---|---|---|
+| BQ-001 | | | | |
+
+## 4. Decision Workflow
+
+Describe how the consumer moves from data to decision to action.
+
+## 5. Trust Expectation Preview
+
+A. Exploratory only  
+B. Internal decision-support with documented limitations  
+C. Trusted shared product with quality checks  
+D. Production-grade with contracts and monitoring  
+
+Current candidate:
+
+## 6. Open Questions
+
+## 7. Assumptions
+
+## 8. Next Workflow
+
+Recommended next:
+
+`dew-kpi-discovery`

package/src/dew-skills/1-analysis/dew-business-discovery/assets/business-question-map-template.md

@@ -0,0 +1,5 @@
+# Business Question Map Template
+
+| Business Question | Consumer | Decision | KPI Candidates | Required Grain | Candidate Sources | Notes |
+|---|---|---|---|---|---|
+| | | | | | | |

package/src/dew-skills/1-analysis/dew-business-discovery/checklist.md

@@ -0,0 +1,12 @@
+# Business Discovery Checklist
+
+- [ ] Project brief loaded or context provided.
+- [ ] At least one data consumer identified.
+- [ ] Core business decision identified.
+- [ ] Business questions mapped to consumers.
+- [ ] Decision-to-action flow described.
+- [ ] Trust expectation previewed.
+- [ ] Unknowns labeled.
+- [ ] Assumptions labeled.
+- [ ] Decision log updated.
+- [ ] Learning log updated if learning mode is enabled.

package/src/dew-skills/1-analysis/dew-business-discovery/customize.toml

@@ -0,0 +1,27 @@
+# DO NOT EDIT -- overwritten on every update.
+#
+# Workflow customization surface for dew-business-discovery.
+
+[workflow]
+
+activation_steps_prepend = []
+activation_steps_append = []
+
+persistent_facts = [
+  "file:{project-root}/**/project-context.md",
+  "file:{project-root}/**/brief.md",
+  "file:{project-root}/**/.decision-log.md",
+  "file:{project-root}/**/.learning-log.md",
+]
+
+on_complete = ""
+
+discovery_template = "assets/business-discovery-template.md"
+question_map_template = "assets/business-question-map-template.md"
+checklist = "checklist.md"
+
+discovery_output_path = "{planning_artifacts}/business-discovery"
+run_folder_pattern = "business-discovery-{project_name}-{date}"
+
+decision_log_path = "{planning_artifacts}/.decision-log.md"
+learning_log_path = "{learning_artifacts}/.learning-log.md"

package/src/dew-skills/1-analysis/dew-decision-gate/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: dew-decision-gate
+description: Run a mandatory DEW decision gate. Use when a project-shaping data engineering decision must be explained, optioned, approved by the user, and recorded before continuing.
+---
+
+# DEW Decision Gate
+
+**Goal:** Force explicit user approval for project-shaping decisions.
+
+**Your Role:** You are a DEW facilitator, not an autonomous decision maker.
+
+You may recommend, but you must not decide.
+
+## 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.
+- `{skill-name}` resolves to the skill directory's basename.
+- `{workflow.<name>}` resolves to fields in `customize.toml`'s `[workflow]` table.
+
+## Mandatory Rules
+
+- Do not silently choose for the user.
+- Do not continue without explicit user approval.
+- Do not treat assumptions as facts.
+- Do not mark a phase complete without evidence.
+- Always record the decision in `.decision-log.md`.
+- Always record learning in `.learning-log.md` when learning mode is enabled.
+
+## 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 each entry in `{workflow.activation_steps_prepend}` in order.
+
+3. Treat every entry in `{workflow.persistent_facts}` as foundational context for the rest of the run. Entries prefixed `file:` are paths or globs under `{project-root}`.
+
+4. Load `{project-root}/_dew/dew/config.yaml` if present and resolve:
+   - `{user_name}`
+   - `{communication_language}`
+   - `{document_output_language}`
+   - `{planning_artifacts}`
+   - `{implementation_artifacts}`
+   - `{project_knowledge}`
+   - `{evidence_artifacts}`
+   - `{learning_artifacts}`
+   - `{learning_mode}`
+
+5. Load:
+   - `{workflow.global_rules}`
+   - `{workflow.gate_catalog}`
+   - `{workflow.gate_template}`
+   - `{workflow.frontmatter_schema}`
+
+6. Greet `{user_name}` in `{communication_language}`.
+
+7. Execute each entry in `{workflow.activation_steps_append}` in order.
+
+## Execution
+
+### Step 1 — Identify gate
+
+Identify:
+- gate ID
+- phase
+- decision needed
+- artifact affected
+- downstream phase affected
+
+If gate ID is unclear, infer the closest gate from `{workflow.gate_catalog}`.
+
+If still unclear, ask the user.
+
+### Step 2 — Explain concept
+
+If `{learning_mode}` is true, explain:
+- what the concept means
+- why it matters in data engineering
+- common mistake
+- downstream impact
+
+### Step 3 — Show evidence
+
+Show:
+- current artifact evidence
+- validation evidence
+- missing evidence
+- assumptions
+- caveats
+
+### Step 4 — Present options
+
+Present 3-5 options.
+
+Each option must include:
+- description
+- pros
+- cons
+- when to choose
+- downstream impact
+
+### Step 5 — Recommend
+
+Recommend one option.
+
+The recommendation must be clearly labeled as recommendation, not decision.
+
+### Step 6 — Ask user
+
+Ask the user to choose:
+
+- A/B/C/D
+- R = revise options
+- E = explain more
+- U = use recommendation
+
+Stop here.
+
+Do not continue until the user explicitly chooses.
+
+### Step 7 — Record
+
+After the user chooses:
+- append to `.decision-log.md`
+- append to `.learning-log.md` if learning mode is enabled
+- update artifact frontmatter if applicable
+- update validation evidence index if applicable
+
+### Step 8 — Resume
+
+Summarize:
+- final decision
+- evidence used
+- caveats
+- downstream impact
+- next step

package/src/dew-skills/1-analysis/dew-decision-gate/assets/decision-gate-template.md

@@ -0,0 +1,147 @@
+# DECISION GATE: {Gate ID} — {Gate Name}
+
+## Gate Type
+
+Soft Halt / Hard Halt / Safety Halt / Readiness Halt
+
+## Phase
+
+{Phase name}
+
+## Trigger
+
+This gate is triggered when:
+- ...
+
+## Why this matters
+
+Explain why this decision affects the project.
+
+Connect the explanation to the data engineering lifecycle:
+- Generation / Source Systems:
+- Storage:
+- Ingestion:
+- Transformation:
+- Serving:
+- Undercurrents:
+
+## Learning explanation
+
+Use this section when `learning_mode = true`.
+
+Explain:
+- concept definition
+- practical example
+- common mistake
+- what can go wrong downstream
+- what evidence is needed
+
+## Current evidence
+
+| Evidence | Status | Path / Reference |
+|---|---|---|
+| Artifact | Available / Missing | |
+| Sample | Available / Missing | |
+| Schema | Available / Missing | |
+| Validation | Available / Missing | |
+| User decision | Available / Missing | |
+
+## Missing evidence
+
+- ...
+
+## Options
+
+### A. {Option A}
+
+Description:
+
+Pros:
+- ...
+
+Cons:
+- ...
+
+Choose this when:
+- ...
+
+### B. {Option B}
+
+Description:
+
+Pros:
+- ...
+
+Cons:
+- ...
+
+Choose this when:
+- ...
+
+### C. {Option C}
+
+Description:
+
+Pros:
+- ...
+
+Cons:
+- ...
+
+Choose this when:
+- ...
+
+### D. {Option D}
+
+Description:
+
+Pros:
+- ...
+
+Cons:
+- ...
+
+Choose this when:
+- ...
+
+## Recommendation
+
+Recommended option: {A/B/C/D}
+
+Reason:
+- ...
+
+## Trade-off summary
+
+| Option | Pros | Cons | Risk | Downstream Impact |
+|---|---|---|---|---|
+| A | | | | |
+| B | | | | |
+| C | | | | |
+| D | | | | |
+
+## Required user decision
+
+Please choose one:
+
+- A
+- B
+- C
+- D
+- R = revise options
+- E = explain more
+- U = use recommendation
+
+## Resume rule
+
+The agent must stop here.
+
+The agent must not continue until the user explicitly selects an option or says “use recommendation”.
+
+## Decision log update required
+
+After the user chooses, append an entry to `.decision-log.md`.
+
+## Learning log update required
+
+After the user chooses, append a short note to `.learning-log.md` when learning mode is enabled.