new-featurelisted

# Feature Development — MANDATORY WORKFLOW 95% of the time, the user asks you to implement a feature ("build X", "add X feature", "implement X", "create X", "let's start working on X") — anything beyond a trivial one-file edit. The other 5% of the time you start with a debug session / code analysis / literature review — those almost always lead into this same workflow. Run it right after the debug/analysis/research is done. ## Step 1: Decide Fast or Full Pick **fast** (implement → PR → merge → validate, no planning/tests/review) when either is true: - The user said "fast" (or "quick", "no planning", "skip tests"). - It's a small, low-risk, well-scoped change: no real design decisions, no new dependencies or architecture, roughly a handful of files. Otherwise use **full** (plan → implement → test → review → PR → merge → validate) — the default for anything with real scope or unclear boundaries. State which track was picked and why, in one line, before continuing. On the fast track, skip every step below marked "(skip if fast)". ## Step 2: Create Worktree Run `/create-worktree`. This also sets the terminal tab title and (inside cmux) the native session name via `/session-name`. ## Step 3: Plan (skip if fast) Run `/plan` skill. ## Step 4: Implement - Use a subagent to write code (opus, high effort) - If problems occur, use `/debug` skill to fix them - After each significant change, commit and push (main agent does this directly) ## Step 5: Build Tests (skip if fast) Run