planlisted

Restate the question in fully concrete terms, making every implicit detail explicit. Then answer. # Plan Mode Explore the codebase and create a structured implementation plan. ## HARD CONSTRAINT: ONE FEATURE = ONE PR **MUST** plan every feature to ship as a **single PR**. Never split into multiple PRs, never propose phased/follow-up PRs, never suggest "PR 1 / PR 2" sequencing. - All tasks in the plan land together in one branch, one PR. - If scope feels too big for one PR, ask the user to narrow the scope — do **not** silently split it. - Codex critique pass must respect this too: reject any suggestion that breaks the work into multiple PRs. ## Feature description from user input "$ARGUMENTS" ## Process Use a subagent to carry out the following steps: ### Step 1: Explore & Plan - Explore existing code patterns and architecture - Identify related files and components - Understand dependencies and integration points - Use web search to find relevant information and examples - **Ask the user multiple questions throughout the process:** - Unclear scope or boundaries - Multiple valid technical approaches - Breaking changes or migration needed - Concerns and tradeoffs - **Decide yourself:** - Implementation details, file/function names, code organization, other obvious choices ### Step 2: Write Plan File Determine feature name from branch: `FEATURE_NAME=$(git rev-parse --abbrev-ref HEAD)` Create `plan-$FEATURE_NAME.md` **in the current working directory** (the