Major improvements to workflow understanding and guidance:
1. New Document: WORKFLOW_DECISION_GUIDE.md
- Comprehensive decision flowchart for full software lifecycle
- Interactive Mermaid diagram with 40+ decision points
- Clear guidance on when to use each command
- Real-world scenarios for all workflow types
- Quick reference tables by knowledge level, project stage, and mode
- Expert tips and common pitfalls
2. Clarified Brainstorm vs Plan Relationship
Core concept correction:
- Brainstorm: Use when you know WHAT to build, NOT HOW
- Plan: Use when you know both WHAT and HOW
- Plan can accept user input OR brainstorm output
3. Updated Documentation Files
- GETTING_STARTED.md: Added clear distinction and decision criteria
- GETTING_STARTED_CN.md: Chinese version with same clarifications
- FAQ.md: Enhanced brainstorm usage explanation with workflow comparison table
- README.md: Added Workflow Decision Guide link
- README_CN.md: Added Chinese link to decision guide
4. Key Improvements
When to Use Brainstorming:
- Unclear solution approach (multiple ways to solve)
- Architectural exploration needed
- Requirements clarification (high-level clear, details not)
- Multiple trade-offs to analyze
- Unfamiliar domain
When to Skip Brainstorming:
- Clear implementation approach
- Similar to existing code patterns
- Well-defined requirements
- Simple features
5. Decision Flowchart Covers:
- Ideation phase (know what to build?)
- Design phase (know how to build?)
- UI design phase (need UI design?)
- Planning phase (complexity level?)
- Testing phase (TDD, post-test, test-fix?)
- Review phase (security, architecture, quality?)
- Completion
Benefits:
- Eliminates confusion about brainstorm usage
- Provides clear decision criteria for all commands
- Visual flowchart helps users navigate workflows
- Comprehensive coverage of all development stages
- Reduces trial-and-error in workflow selection
Files modified: 5
Files added: 1 (WORKFLOW_DECISION_GUIDE.md)
