dev-definelisted

# Feature Definition PHASE 1 of the dev workflow: define → build → test. **Trigger**: `/dev-define` or `/dev-define [feature-name]` ## Constraints (apply to every phase) - **No implementation code anywhere.** Plan file and feature.json contain only type signatures, structure, decisions. Function bodies, `(set, get) => ({...})` blocks, JSX, hook internals → `/dev-build`. Detail: see PHASE 2 "Strict boundary." - **No requirements skipping** — every feature gets PHASE 1 extraction with acceptance criteria. - **No phase-jump without checkpoint** — user confirms scope (PHASE 1) before architecture; user approves plan (PHASE 2) before feature.json write. - **Plan mode active before any analytical step** — `EnterPlanMode` MUST be called immediately after TaskCreate + setup writes (mkdir, session file) and BEFORE the first `Read`, `Glob`, `Grep`, or `AskUserQuestion` in this skill. The interview (PHASE 1a) must run inside plan mode so model routers (e.g. `opusplan`) route it through the planning model. `ExitPlanMode` at end of PHASE 2; PHASE 3+4 run after approval. ## Workflow **Phase tracking** — first action of the skill: call `TaskCreate` with these 3 items (status `pending`), then use `TaskUpdate` to set each phase to `in_progress` at the start and `completed` at the end. During context compaction the task list remains visible — no risk of forgetting phases. 1. PHASE 0+1a+1b: Setup, Plan Mode, Context, Interview & Requirements 2. PHASE 2: Architecture 3. PHASE 3+4: feature