| name | plan-feature |
| description | Plan a new feature before writing code. Explores the codebase, creates a structured plan with verification criteria, and only implements after approval. |
| disable-model-invocation | true |
| argument-hint | ["feature description"] |
Plan Feature
Create a structured implementation plan before writing any code. Based on the principle that planning before coding prevents wasted work and produces better results.
Usage
/plan-feature <description of the feature>
Procedure
Step 1: Understand the Request
Parse $ARGUMENTS to understand what feature the user wants. If the description is ambiguous, ask clarifying questions:
- What is the expected behavior?
- Are there any constraints (performance, compatibility, etc.)?
- Should this follow an existing pattern in the codebase?
Step 2: Explore the Codebase
Before planning, understand the existing architecture. Use the Explore agent or read files directly:
- Find related code: Search for files related to the feature (e.g., if adding auth, search for existing auth/user code)
- Understand patterns: How does the codebase structure similar features? (routing, services, models, tests)
- Identify dependencies: What existing modules will this feature interact with?
