plan-feature

# Plan Feature (router) The engineering-planning door for a feature whose product definition already exists. Routes to a focused internal step so only the work you need runs (no fat single skill). **Docs only — no code, no branch.** Product definition (raw-idea interview, capability closure) is `design-feature`'s job, not this one — see the redirect gate below. ## Turn contract — verify before ending the turn ``` ✓ The redirect gate ran FIRST, before any SPEC edit: undesigned input → STOP, print the fixed `/design-feature <slug>` block, do nothing else this turn ✓ Designed input only: engineering half filled, artifacts written, and the roadmap entry registered (number, order, deps verified) ✓ If `plan-feature-scaffold` ran this turn: the roadmap row was re-read AFTER the write and literally reads `planned` — a dropped `defined→planned` write fails this box; do not end the turn until it's fixed ✓ The dependency & blocker check was RUN and its result decides which closing block is printed ✓ Artifact language: explicit user instruction > the project's declared docs language > English. The CONVERSATION language never decides — a Spanish prompt still produces English PRs/issues/commits/SPECs unless one of the first two says otherwise ✓ The closing `→ Next:` block is printed as the ABSOLUTE last output ``` About to end the turn with any box unchecked? The turn is NOT done — complete the missing box first (weak models drop end-of-document duties; this list is first on pu...