ddw-verify-modulelisted

# Skill: /ddw-verify-module ## Description Verifies that a completed module meets every acceptance criterion in its PRD and every task in its spec. A blocking gate. ## Inputs - The PRD at `docs/ddw/prd/prd-{ticket}.md` (if `gates.define` is true and the tier is FEATURE). - The spec/fix-plan at `docs/ddw/specs/spec-{ticket}.md` or `docs/ddw/specs/fix-{ticket}.md` (if `gates.spec` is true). - The implemented code. - The tests, and their results. - `.ddw/rules/validation-rules.instructions.md` §5 for the rules (F-VER-01 to F-VER-06, W-VER-01 to W-VER-03) — the single source of truth. - The `tier` from `.ddw-state.json`. ## Execution Protocol ### For FEATURE 1. **Verify the PRD's acceptance criteria** (F-VER-01): For EVERY acceptance criterion: - Does the code implement it? (exact location: file:function) - Is there a test verifying it — and is that test passing? - Does the test verify the actual behavior, or only the status code? Status-code-only is a WARNING, not a PASS. 2. **Verify the spec's tasks** (F-VER-02, F-VER-06): For EVERY checkbox in the spec: - Is it marked complete? - Does the corresponding code exist? - Does every test the spec listed exist and pass? Those are approved commitments. 3. **Verify coverage** (F-VER-03): - Lines ≥ 80%, branches ≥ 80%, functions ≥ 80% over the new/modified code. Below any of them is a FAIL, not a warning. - Core business logic between 80–90% is a WARNING (W-VER-02): it should be higher.