stdd-planlisted

# stdd-plan — Map（行軍圖） Third phase of the STDD pipeline (`stdd-explore → stdd-uiux (conditional) → stdd-spec → stdd-plan → stdd-execute`). Turns an approved `spec.md` into condition-based design artifacts and a scenario-covered `tasks.md`. Canonical spec: `STDD/specs/stdd-plan.md` (REQ-03); cross-cutting mechanisms (frontmatter status fields, dual-fingerprint rule, wiki/ taxonomy, Lint-STOP rule) are canonical in `STDD/spec.md` — this skill references them, it does not restate them. Worked examples: `templates/design-be.md`, `templates/tasks.md`. Distilled references: `references/openapi-skeleton.md`, `references/23-design-patterns.md`. ## Resuming an interrupted run Each step below writes one line to `.progress.log` in the change directory (`STDD/<name>/.progress.log`) when it starts and again when it finishes: `START <step-name>` / `DONE <step-name>`. On re-entry into this skill for a change directory that already has a `.progress.log`, read it first, find the last `DONE` line, and resume from the step after it — do not re-run already-`DONE` steps from scratch. Delete `.progress.log` once the approval gate (step 7) completes; a leftover file after approval is a bug, not a valid resume point. ## 0. Gate check (precondition, spec S-06/S-08) Before doing anything else, read `STDD/<name>/spec.md` frontmatter (and `STDD/<name>/design-ux.md`'s existence, if any): - If `spec.md` `status` is not `approved` → **refuse to run**, report why, and stop. Do not produce any design