Guide users from app idea to feature breakdown to implementation specs. Use when the user has an app idea but no features defined yet, wants to start a new project from scratch, or needs help breaking down an app concept into implementable features.
Transform app ideas into structured feature lists and complete specifications.
Use this skill when:
Ask Discovery Questions:
Feature Categories to Consider:
User Management:
Core Functionality:
Discovery & Navigation:
Social/Collaborative:
Content Management:
Help User Prioritize:
Essential (MVP):
- [Features needed for basic functionality]
Important (Phase 2):
- [Features that enhance core value]
Nice-to-Have (Future):
- [Features that can wait]
For each essential feature, create:
## Feature: [Name]
**User Need**: [What user problem this solves]
**Priority**: Essential / Important / Nice-to-Have
**Estimated Complexity**: Simple / Medium / Complex
**Dependencies**: [What must exist first]
**User Stories** (preliminary):
- As a [user], I want to [action], so that [benefit]
**Next Step**: Create complete spec for this feature
Recommend implementation order:
Foundation Features (always first):
Core Value Features (next):
Enhancement Features (later):
For each feature in sequence:
Now let's create complete specs for: [Feature Name]
Use spec-orchestrator or commands:
@spec-orchestrator create spec for [feature]
or
/spec-workflow [feature-name]
This will create:
- Requirements (with EARS acceptance criteria)
- Design (architecture and components)
- Tasks (implementation breakdown)
Use this structure:
# App Plan: [App Name]
## Vision
[What is this app? Who is it for? What problem does it solve?]
## Target Users
- Primary: [Main user type]
- Secondary: [Other user types]
## Core Value Proposition
[The main thing this app does that provides value]
## Platform & Technology
- Platform: [Web / Mobile / Desktop / All]
- Frontend: [Technology choice]
- Backend: [Technology choice]
- Database: [Technology choice]
## Feature Breakdown
### Essential Features (MVP)
1. **[Feature 1]**
- User Need: [What problem this solves]
- Complexity: [Simple/Medium/Complex]
- Dependencies: [Prerequisites]
- Status: [ ] Planned → [ ] Spec Created → [ ] Implemented
2. **[Feature 2]**
...
### Important Features (Phase 2)
[Features for version 2]
### Nice-to-Have (Future)
[Features that can wait]
## Implementation Sequence
Phase 1 - Foundation:
- [ ] Feature A
- [ ] Feature B
Phase 2 - Core Value:
- [ ] Feature C
- [ ] Feature D
Phase 3 - Enhancement:
- [ ] Feature E
- [ ] Feature F
## Next Steps
1. Create spec for [first feature]
2. Implement first feature
3. Test and validate
4. Move to next feature
User Says: "I want to build a recipe sharing app"
App Planning Response:
# App Plan: Recipe Sharing App
## Vision
A platform where home cooks can share, discover, and save recipes.
## Target Users
- Home cooks who want to share recipes
- People looking for new recipes to try
- Users organizing their recipe collection
## Core Value Proposition
Easy recipe sharing with great discovery and organization tools.
## Feature Breakdown
### Essential Features (MVP)
1. **User Authentication**
- User Need: Secure accounts to save recipes and follow others
- Complexity: Medium
- Dependencies: None (foundation feature)
- Status: [ ] Planned
2. **Recipe Creation**
- User Need: Share recipes with ingredients and instructions
- Complexity: Medium
- Dependencies: User Authentication
- Status: [ ] Planned
3. **Recipe Browsing**
- User Need: Discover recipes from other users
- Complexity: Simple
- Dependencies: Recipe Creation
- Status: [ ] Planned
4. **Recipe Saving**
- User Need: Save favorite recipes to personal collection
- Complexity: Simple
- Dependencies: User Authentication, Recipe Browsing
- Status: [ ] Planned
### Important Features (Phase 2)
5. **Search & Filters**
- User Need: Find specific recipes quickly
- Complexity: Medium
6. **Recipe Ratings & Comments**
- User Need: Get feedback and help others
- Complexity: Medium
7. **User Profiles**
- User Need: Follow favorite recipe creators
- Complexity: Simple
### Nice-to-Have (Future)
8. **Meal Planning**
9. **Shopping Lists**
10. **Nutrition Information**
## Implementation Sequence
**Phase 1 - Foundation (Week 1-2)**:
- [ ] User Authentication → Create spec: /spec-workflow user-authentication
- [ ] Recipe Data Model → Create spec: /spec-workflow recipe-management
**Phase 2 - Core Value (Week 3-4)**:
- [ ] Recipe Creation → Create spec: /spec-workflow recipe-creation
- [ ] Recipe Browsing → Create spec: /spec-workflow recipe-browsing
- [ ] Recipe Saving → Create spec: /spec-workflow recipe-saving
**Phase 3 - Enhancement (Week 5-6)**:
- [ ] Search & Filters → Create spec: /spec-workflow search-filters
- [ ] Ratings & Comments → Create spec: /spec-workflow ratings-comments
## Next Step
Let's start with User Authentication:
@spec-orchestrator create spec for user authentication
After app planning:
✅ App Plan Complete: Recipe Sharing App
You have 7 features identified.
Ready to create specs? Start with:
Option 1: One at a time (recommended)
@spec-orchestrator create spec for user-authentication
Option 2: Batch create
/spec-workflow user-authentication
/spec-workflow recipe-creation
/spec-workflow recipe-browsing
...
Option 3: Create worktrees for parallel work
/spec-workflow user-authentication
/create_worktree user-authentication
/spec-workflow recipe-creation
/create_worktree recipe-creation
Essential: User auth, profiles, content creation, feed, following Important: Search, notifications, messaging Nice-to-Have: Stories, live features, advanced algorithms
Essential: Product catalog, cart, checkout, orders Important: Search/filters, reviews, user accounts Nice-to-Have: Recommendations, wishlists, gift cards
Essential: Core workflow, data management, basic organization Important: Search, filters, collaboration Nice-to-Have: Integrations, automation, analytics
Essential: Content creation, viewing, basic discovery Important: Search, categories, user engagement Nice-to-Have: Recommendations, social features, monetization
App Planning bridges idea → features → specs:
Then implement feature by feature, spec by spec, systematically building your app!