Plan Feature
Use this skill when the request is large enough, ambiguous enough, or risky enough that a plan is more useful than immediate edits.
Workflow
- •Restate the goal in terms of user-visible outcome and non-goals.
- •Read the relevant code paths before proposing changes.
- •Break the work into a small number of slices with clear boundaries.
- •For each slice, note likely files, data flow, edge cases, and the verification needed.
- •Call out migration, compatibility, and rollback risks early.
- •Prefer the smallest shippable version before follow-up polish.
Output
- •Goal and constraints
- •Proposed approach
- •Implementation slices
- •Risks and unknowns
- •Verification plan
Avoid
- •Do not jump straight into code without reading source
- •Do not propose unrelated refactors
- •Do not leave validation as a vague final step