plan when the task needs scope, sequencing, or tradeoff review before edits.
When to use it
Use plan for | Use another skill for |
|---|---|
| Multi-file changes | One small copy edit |
| Architecture or data-flow choices | A known failing test |
| Work that needs approval before edits | A direct implementation request |
What to provide
| Input | Example |
|---|---|
| Outcome | Add usage-based billing. |
| Constraints | Keep the existing Stripe integration. |
| Scope | Cover API routes, UI states, and tests. |
| Verification | Include the checks that prove the change works. |
Example request
Expected output
Agent returns a structured plan with scope, steps, risks, and verification. Use the plan as the handoff forbuild when the direction is clear.
Related
| Page | Use it to |
|---|---|
| Build skill | Implement an approved plan. |
| Review skill | Check the result before merge. |