// Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
| name | feature-planning |
| description | Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change. |
Systematically analyze feature requests and create detailed, actionable implementation plans.
Ask clarifying questions:
Explore the codebase:
Use Task tool with subagent_type='Explore' and thoroughness='medium' to understand:
Identify components:
Consider architecture:
Check dependencies:
Break feature into discrete, sequential tasks:
## Feature: [Feature Name]
### Overview
[Brief description of what will be built and why]
### Architecture Decisions
- [Key decision 1 and rationale]
- [Key decision 2 and rationale]
### Implementation Tasks
#### Task 1: [Component Name]
- **File**: `path/to/file.py:123`
- **Description**: [What needs to be done]
- **Details**:
- [Specific requirement 1]
- [Specific requirement 2]
- **Dependencies**: None (or list task numbers)
#### Task 2: [Component Name]
...
### Testing Strategy
- [What types of tests needed]
- [Critical test cases to cover]
### Integration Points
- [How this connects with existing code]
- [Potential impacts on other features]
Include specific references:
src/utils/auth.py:45)Confirm:
Launch plan-implementer agent for each task:
Task tool with:
- subagent_type: 'plan-implementer'
- description: 'Implement [task name]'
- prompt: Detailed task description from plan
Execution strategy:
Planning:
Communication:
Execution:
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
Analyze files and get detailed metadata including size, line counts, modification times, and content statistics. Use when users request file information, statistics, or analysis without modifying files.
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.