mhattingpete/claude-skills-marketplace / engineering-workflow-plugin/skills/feature-planning
feature-planning
VerifiedBreak down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Feature Planning
Systematically analyze feature requests and create detailed, actionable implementation plans.
When to Use
- Requests new feature ("add user authentication", "build dashboard")
- Asks for enhancements ("improve performance", "add export")
- Describes complex multi-step changes
- Explicitly asks for planning ("plan how to implement X")
- Provides vague requirements needing clarification
Planning Workflow
1. Understand Requirements
Ask clarifying questions:
- What problem does this solve?
- Who are the users?
- Specific technical constraints?
- What does success look like?
Explore the codebase:
Use Task tool with subagent_type='Explore' and thoroughness='medium' to understand:
- Existing architecture and patterns
- Similar features to reference
- Where new code should live
- What will be affected
2. Analyze & Design
Identify components:
- Database changes (models, migrations, schemas)
- Backend logic (API endpoints, business logic, services)
- Frontend changes (UI, state, routing)
- Testing requirements
- Documentation updates
Consider architecture:
- Follow existing patterns (check CLAUDE.md)
- Identify reusable components
- Plan error handling and edge cases
- Consider performance implications
- Think about security and validation
Check dependencies:
- New packages/libraries needed
- Compatibility with existing stack
- Configuration changes required
3. Create Implementation Plan
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:
- File paths with line numbers (
src/utils/auth.py:45) - Existing patterns to follow
- Relevant documentation
4. Review Plan with User
Confirm:
- Does this match expectations?
- Missing requirements?
- Adjust priorities or approach?
- Ready to proceed?
5. Execute with plan-implementer
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:
- Implement sequentially (respect dependencies)
- Verify each task before next
- Adjust plan if issues discovered
- Let test-fixing skill handle failures
- Let git-pushing skill handle commits
Best Practices
Planning:
- Start broad, then specific
- Reference existing code patterns
- Include file paths and line numbers
- Think through edge cases upfront
- Keep tasks focused and atomic
Communication:
- Explain architectural decisions
- Highlight trade-offs and alternatives
- Be explicit about assumptions
- Provide context for future maintainers
Execution:
- Implement one task at a time
- Verify before moving forward
- Keep user informed
- Adapt based on discoveries
Integration
- plan-implementer agent: Receives task specs, implements
- test-fixing skill: Auto-triggered on test failures
- git-pushing skill: Triggered for commits
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |