harrymunro/ralph-wiggum/planning

Round [N] complete. [5-N] rounds remaining.

Round 5 complete. Planning session finished.

1. What specific problem are we trying to solve?
   A. Users cannot do X at all
   B. Users can do X but it's slow/painful
   C. Users frequently make mistakes doing X
   D. Other: [please specify]
 
2. Who experiences this problem most acutely?
   A. New users during onboarding
   B. Power users doing advanced tasks
   C. All users equally
   D. Internal team members
 
3. What happens today when users encounter this problem?
   A. They work around it manually
   B. They contact support
   C. They abandon the task
   D. They use a competitor

## Round 1 Summary: Problem Understanding
- Problem: [concise problem statement]
- Affected users: [who]
- Current workaround: [what they do now]
- Impact: [why it matters]

1. What is the minimum viable version of this feature?
   A. Just the core functionality, no polish
   B. Core + basic UI polish
   C. Full feature set with advanced options
   D. Let me describe: [specify]
 
2. Which of these are must-haves vs nice-to-haves?
   [List potential features, ask user to categorize]
 
3. What should this feature explicitly NOT do?
   A. No integration with external services
   B. No admin configuration options
   C. No mobile-specific features
   D. Other: [specify]
 
4. Are there adjacent features we should leave alone?
   A. Yes: [list them]
   B. No, we can modify anything needed

## Round 2 Summary: Scope Definition
- MVP includes: [list]
- Nice-to-haves (not MVP): [list]
- Explicitly out of scope: [list]
- Do not touch: [list of adjacent features to avoid]

1. What existing systems will this feature interact with?
   A. Database only
   B. Database + existing API endpoints
   C. Database + API + external services
   D. Let me list: [specify]
 
2. Are there performance requirements?
   A. Must handle X requests per second
   B. Must respond within X milliseconds
   C. No specific requirements
   D. Other: [specify]
 
3. Are there security considerations?
   A. Handles sensitive user data
   B. Requires authentication checks
   C. Needs rate limiting
   D. No special security needs
 
4. What existing code patterns should we follow?
   A. Follow existing patterns in [module]
   B. This is a new pattern for the codebase
   C. Not sure, needs investigation

## Round 3 Summary: Technical Constraints
- Systems affected: [list]
- Database changes: [yes/no, what]
- API changes: [yes/no, what]
- Performance requirements: [list]
- Security considerations: [list]
- Patterns to follow: [reference]

1. What should happen when [primary action] fails?
   A. Show error message and let user retry
   B. Automatically retry X times
   C. Fall back to [alternative behavior]
   D. Other: [specify]
 
2. What about empty states (no data yet)?
   A. Show helpful empty state with CTA
   B. Show nothing
   C. Show sample/demo data
   D. Other: [specify]
 
3. What about existing users/data?
   A. Migration needed for existing data
   B. Feature only applies to new data
   C. Backfill existing data automatically
   D. Let users manually migrate
 
4. What if user does something unexpected?
   [List specific unexpected behaviors and ask how to handle]

## Round 4 Summary: Edge Cases
- Error handling: [approach]
- Empty states: [approach]
- Data migration: [approach]
- Unexpected user behavior: [list with handling]
- Concurrent operations: [approach]

1. What automated tests should cover this feature?
   A. Unit tests for core logic
   B. Integration tests for API endpoints
   C. E2E tests for user flows
   D. All of the above
 
2. What manual testing is required?
   A. Visual inspection of UI changes
   B. Testing edge cases in browser
   C. Testing with different user roles
   D. List specific scenarios: [specify]
 
3. How do we know this feature is successful in production?
   A. Users complete [action] X% more often
   B. Support tickets about [topic] decrease
   C. Feature adoption reaches X%
   D. Other metrics: [specify]
 
4. What should we monitor for issues?
   A. Error rates on new endpoints
   B. Performance metrics
   C. User feedback/complaints
   D. All of the above

## Round 5 Summary: Verification Strategy
- Automated tests: [list]
- Manual testing: [list]
- Success metrics: [list]
- Monitoring: [list]

# Planning Summary: [Feature Name]
 
Generated: [Date]
Status: Ready for PRD
 
---
 
## Round 1: Problem Understanding
[Summary from Round 1]
 
## Round 2: Scope Definition
[Summary from Round 2]
 
## Round 3: Technical Constraints
[Summary from Round 3]
 
## Round 4: Edge Cases
[Summary from Round 4]
 
## Round 5: Verification Strategy
[Summary from Round 5]
 
---
 
## Next Steps
 
1.Create PRD using `/prd` skill
2.Convert to `prd.json` using `/ralph` skill
3.Run Ralph to implement