designlisted

# /design — Design + Plan (alias: /2) **Trigger:** New features, spec gaps, design decisions needed. **Channel:** CT=`CURRENT_TASK_chN.md` (channeled) or `CURRENT_TASK.md`. Scripts: `SENTINEL_CHANNEL=N`. `[chN/]`=dispatch subdir, `[_chN]`=file suffix, `[chN_]`=squad prefix. Full rules: `.claude/reference/channel-routing.md`. **Step 0:** Before any other work, TaskCreate every step. Mark in_progress→completed. ## Logical ordering (read first) The /design pipeline produces two artifacts that derive from each other: the **spec** (output of brainstorming) and the **plan** (output of writing-plans, consumed by /3). Each artifact must be verified BEFORE downstream work consumes it. Spec-verify therefore runs BEFORE writing-plans, not after — otherwise the plan derives from an unverified spec and any spec-level issue forces a plan rewrite, wasting plan-writing work. Order: brainstorm → spec → **experiential walkthrough** → **/verify spec** → writing-plans → classify + consolidate → decision externalization → scrap-and-rewrite CT → **/verify plan** → (situational) **/verify external-tool prompt** → generate Sonnet specs → user approval. ## Procedure ### Step 1: Brainstorm Invoke `superpowers:brainstorming` skill. Flow: brainstorm → spec doc. The spec is the input to Step 1b. ### Step 1b: Experiential walkthrough (MANDATORY before /verify) Code is in service to user experience, not the other way around. Before /verify (which checks rigor, not coherence), narrate the user's