- Updated all references from `/workflow:action-plan-verify` to `/workflow:plan-verify` across various documentation and command files.
- Introduced a new command file for `/workflow:plan-verify` that performs read-only verification analysis on planning artifacts.
- Adjusted command relationships and help documentation to reflect the new command structure.
- Ensured consistency in command usage throughout the workflow guide and getting started documentation.
Addresses issue #33 - /cli:mode:bug-diagnosis command not found
Changes:
- Remove deprecated /cli:* commands (/cli:analyze, /cli:chat, /cli:execute,
/cli:codex-execute, /cli:discuss-plan, /cli:mode:*) from documentation
- Only /cli:cli-init remains as the sole CLI command
- Update all references to use /workflow:lite-plan, /workflow:lite-fix
- Clarify that CLI tools are now invoked through semantic invocation
(natural language) - Claude auto-selects Gemini/Qwen/Codex with templates
- Update COMMAND_SPEC.md, COMMAND_REFERENCE.md, GETTING_STARTED*.md,
FAQ.md, WORKFLOW_DECISION_GUIDE*.md, workflow-architecture.md
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
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)
Add four new comprehensive documentation files and update READMEs:
New Documentation:
- ARCHITECTURE.md: High-level system architecture overview
* Design philosophy and core principles
* System components and data flow
* Multi-agent system details
* CLI tool integration strategy
* Session and memory management
* Performance optimizations and best practices
- CONTRIBUTING.md: Contributor guidelines
* Code of conduct
* Development setup instructions
* Coding standards and best practices
* Testing guidelines
* Documentation requirements
* Pull request process
* Release process
- FAQ.md: Frequently asked questions
* General questions about CCW
* Installation and setup
* Usage and workflows
* Commands and syntax
* Sessions and tasks
* Agents and tools
* Memory system
* Troubleshooting
* Advanced topics
- EXAMPLES.md: Real-world use cases
* Quick start examples
* Web development (Express, React, e-commerce)
* API development (REST, GraphQL)
* Testing & quality assurance (TDD, test generation)
* Refactoring (monolith to microservices)
* UI/UX design (design systems, landing pages)
* Bug fixes (simple and complex)
* Documentation generation
* DevOps & automation (CI/CD, Docker)
* Complex projects (chat app, analytics dashboard)
Updated Documentation:
- README.md: Added comprehensive documentation section
* Organized docs into categories
* Links to all new documentation files
* Improved navigation structure
- README_CN.md: Added documentation section (Chinese)
* Same organization as English version
* Links to all documentation resources
Benefits:
- Provides clear entry points for new users
- Comprehensive reference for all features
- Real-world examples for practical learning
- Complete contributor onboarding
- Better project discoverability
