design-featurelisted

# Design Feature Product definition — the stage that turns an idea or a feature request into an exhaustive, checkable set of acceptance criteria, before any engineering planning happens. **Docs only — no code, no branch.** ## Turn contract Load and verify the **canonical** [Turn contract](.claude/skills/orchestration-envelope/references/TURN_CONTRACT.md) (11 boxes) before ending every turn. Design-specific closure boxes (product half, capability/role matrix, expectation sweep, upsert) live only in [INTERVIEW.md](references/INTERVIEW.md). Missing reference → STOP. ## When to use - A rough idea, no issue yet, and no SPEC: `design-feature "<idea>"`. - An existing feature slug whose SPEC is not yet marked `designed`: `design-feature <NN-slug>`. - Revising an already-designed feature's product definition: `design-feature <NN-slug> "<change>"` (instruction mode), or bare `design-feature <NN-slug>` for review mode (see *Interaction & upsert*). - `plan-feature` redirects here when it detects an undesigned feature or a product choice a `review-spec` `NEEDS-DESIGN` verdict returned to the human. ## Step 0 — Discover the project (always first) Per the agent guide's **Workflow conventions** + **documentation map**, then read what THIS skill needs: `docs/features/_TEMPLATE/SPEC.md` (the two-halves layout + `## Design status` marker), the roadmap (`docs/features/ROADMAP.md`), the **capability inventory** (`docs/CAPABILITIES.md` — the substrate the Integration closure walks;