plan-featurelisted

# Plan Feature Run a structured planning conversation for a new feature or phase in an **existing** project, then produce a scoped plan document. Unlike plan-init (greenfield), this skill starts by reading what already exists so questions focus only on the delta. ## Invocation ```text /plan-feature [optional: feature name or one-liner] ``` If the user provides a feature name or description inline, use it to seed Phase 2 and skip redundant questions. ## Pipeline position Step 1 of the plan pipeline: `plan-feature → plan-review → plan-wrap → repo-sync → build-phase`. `/plan-expedite` autonomously chains the three intermediate stages (`plan-review-autofix → plan-wrap-autofix → repo-sync → session-wrap`) so `/build-phase` gets a clean, sync'd plan to walk. Always surface the closing-message contract below so the chain can't be skipped accidentally. After writing the plan file, end your turn by surfacing the recommended next move: the produced plan must pass `/plan-review` and `/plan-wrap` BEFORE `/repo-sync` mints GitHub issues — a gap caught after sync is an **N+1-edit** problem (1 plan-doc fix + N issue-body edits). The autonomous chain that handles this for you is `/plan-expedite --plan documentation/<slug>-plan.md`, followed by `/build-phase --plan documentation/<slug>-plan.md` once `/plan-expedite` returns READY. ## Before the conversation — auto-discovery Before asking anything, silently read and internalize: 1. **Producing files for any value the feature will ref