feature-planning
Feature Planning transforms vague feature requests into structured implementation roadmaps. It systematically clarifies requirements, explores your codebase for patterns, designs components, and generates discrete, sequenced tasks with file paths and dependencies. Integrates with plan-implementer to execute each task.
Feature Planning breaks down feature requests into detailed, sequential implementation tasks with specific file references and architecture decisions.
AI-generated summary based on this skill's SKILL.md
Install
mhattingpete/claude-skills-marketplace/feature-planning · repository language: HTML
git clone https://github.com/mhattingpete/claude-skills-marketplace
cp -r claude-skills-marketplace/engineering-workflow-plugin/skills/feature-planning ~/.claude/skills/feature-planningFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does feature-planning turn a feature request into an actionable plan?
Feature Planning transforms vague feature requests into structured implementation roadmaps by systematically clarifying requirements, exploring your codebase for patterns, designing components, and generating discrete, sequenced tasks with file paths and dependencies. It breaks down complex requests into detailed, actionable steps you can execute step-by-step.
Can feature-planning help me break down a feature request into tasks?
Yes. Feature Planning specializes in breaking down feature requests into detailed, actionable implementation plans. It analyzes your requirements, creates systematic architecture designs, and plans complex multi-step changes with clear task sequencing. Each task includes specific file paths and dependency information to guide development.
What does feature-planning generate for complex feature changes?
Feature Planning generates implementation roadmaps with file paths and dependencies for complex multi-step changes. It sequences tasks logically, identifies architectural decisions needed, explores existing code patterns, and structures the entire development workflow so you know exactly what to build and in what order.
How does feature-planning clarify vague or unclear feature requests?
Feature Planning uses structured questioning to clarify vague feature requests. It systematically analyzes ambiguous requirements, asks targeted questions about scope and intent, and refines the specification before creating your implementation plan. This ensures your roadmap addresses the actual need, not assumptions.
Does feature-planning integrate with other tools for execution?
Feature Planning integrates with plan-implementer to execute each task in your roadmap. After Feature Planning generates your structured implementation plan with sequenced tasks and dependencies, plan-implementer can take over to implement each step, keeping your development workflow continuous and coordinated.
What license does feature-planning use?
Feature Planning is released under the Apache-2.0 license, which permits commercial and private use, modification, and distribution with proper attribution and license inclusion.
SKILL.md
rendered from the published skill — quoted content, verbatim
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,
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 2 files
engineering-workflow-plugin/skills/feature-planning/SKILL.md
engineering-workflow-plugin/skills/feature-planning/references/planning-best-practices.md