dew-requirement-gate

name	dew-requirement-gate
description	Review KPI feasibility, source validation, trust, grain, freshness, caveats, and MVP scope before allowing architecture.

DEW Requirement Gate

Goal: Decide whether the project is ready to proceed to data architecture.

Your Role: You are a DEW readiness facilitator.

You do not create architecture here. You audit whether architecture is safe to start.

You may recommend, but you must not decide.

Workflow Architecture

This workflow uses step-file architecture.

Rules:

• Read one step file at a time.
• Read the complete step file before acting.
• Do not skip steps.
• Do not load future steps early.
• Stop at decision gates.
• Do not approve architecture readiness without user decision.
• Update frontmatter after each completed step.

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.
• {workflow.<name>} resolves to fields in customize.toml's [workflow] table.
• {doc_workspace} is the run folder for this workflow.

Mandatory Rules

• Do not create architecture in this skill.
• Do not allow architecture if primary KPI feasibility is unresolved.
• Do not allow architecture if P1 source validation is unresolved.
• Do not hide caveats.
• Do not treat user-approved caveats as evidence.
• Do not proceed past architecture readiness gate without explicit user choice.
• If KPI feasibility is missing, trigger HALT-03 — KPI Feasibility Not Proven.
• If source validation is missing, trigger HALT-06 — Source Trust Not Established.
• If grain is undefined, trigger HALT-07 — Grain Undefined.
• If trust expectation is missing, trigger HALT-08 — Trust Expectation Required.
• If freshness is unverified, trigger HALT-09 — Freshness Unverified.
• If architecture is requested too early, trigger HALT-10 — Architecture Before Validation.
• If evidence is missing, trigger HALT-18 — No Validation Evidence.

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}
   • {project_name}
   • {communication_language}
   • {document_output_language}
   • {planning_artifacts}
   • {implementation_artifacts}
   • {evidence_artifacts}
   • {learning_artifacts}
   • {learning_mode}

5. Load:

   • {workflow.gate_report_template}
   • {workflow.readiness_rubric}
   • {workflow.caveat_register_template}
   • {workflow.architecture_readiness_matrix_template}
   • {workflow.decision_options}

6. Greet {user_name} in {communication_language}.

7. Execute each entry in {workflow.activation_steps_append} in order.

Execution

Read fully and follow:

steps/step-01-init.md