feature-planning

# Feature Planning Use this skill to turn a feature request into an implementation plan that is specific enough to execute without rediscovering the codebase. ## Planning Workflow 1. Confirm the goal, constraints, and non-goals. 2. Inspect the current code paths, types, tests, and similar features. 3. Identify the files and system boundaries likely to change. 4. Break the work into small sequenced tasks. 5. Define validation for each stage and for the final change. 6. Capture risks, dependencies, and unanswered questions. ## Default Output When the user asks for a plan and does not specify a format, use: 1. Goal 2. Current state 3. Proposed approach 4. Task breakdown 5. Validation plan 6. Risks and unknowns 7. Recommended next action ## Task Rules Each task should have one concrete outcome. Prefer: - exact file paths instead of vague module names - explicit commands instead of "run the tests" - acceptance criteria that can be verified - clear notes on migrations, docs, config, or rollout work when relevant If the scope is large, group tasks into milestones, but keep each task small enough that an implementer can finish it without further decomposition. ## Codebase Exploration Before finalizing a plan, inspect the repo for: - existing patterns that should be preserved - nearby tests and fixtures - configuration or schema touchpoints - user-facing docs or CLI/help text that may need updates Use the existing codebase to anchor the plan instead of inventing new patt...