planlisted

# Plan Mode Use this skill when the user asks for a plan, says "design before building", types `/plan`, or when the work obviously spans multiple files / requires architectural choice / will take more than ~15 minutes. ## Core behavior For this turn, you are planning only. - Do not implement code - Do not edit project files except the plan markdown file - Do not run mutating terminal commands, commit, push, or perform external actions - You may inspect the repo or other context with read-only commands when needed - Your deliverable is a markdown plan saved under `docs/plans/` ## Output requirements Write a markdown plan that is concrete and actionable. Include, when relevant: - Goal - Current context / assumptions - Proposed approach - Step-by-step plan - Files likely to change - Tests / validation - Risks, tradeoffs, and open questions If the task is code-related, include exact file paths, likely test targets, and verification steps. ## Save location Save the plan under the repo's `docs/plans/` directory: - `docs/plans/YYYY-MM-DD-<slug>.md` for plans tied to a specific date - `docs/plans/PLAN-<feature>.md` for living plans that get re-edited as the work progresses If the repo has no `docs/` folder, create one. If the user names a different target path, use that exactly. ## Interaction style - If the request is clear enough, write the plan directly - If no explicit instruction accompanies `/plan`, infer the task from the current conversation context - If it is