Role-Driven Development Workflow for Claude Code

License: MIT Release Validate Plugin GitHub stars Homepage

English | 中文 | 🌐 Homepage

Transform Claude into a complete development team. From product requirements to code review — one plugin, full workflow.

44 commands · 19 skills · 8 agents · 43 rules · 30 hooks

CC-Best autonomous iteration demo

Quick Start • Features • Workflow • Commands • FAQ

🎯 The Problem: Claude Code is powerful, but configuring workflows, coding standards, and safety rules from scratch takes hours.

✨ The Solution: Pre-configured roles (PM → Lead → Designer → Dev → QA) that mirror real team collaboration, with safety guardrails built-in.

# Add marketplace and install
/plugin marketplace add xiaobei930/cc-best
/plugin install cc-best@xiaobei930
# Verify installation (30 seconds)
/cc-best:status
# Start using
/cc-best:iterate "implement user authentication"

💡 Enable Hooks: After installation, run /cc-best:setup --hooks to activate safety guards and automation hooks. See Hooks Configuration for details.

💡 Recommended: Install via plugin for automatic updates and easier management. All documentation uses plugin format (/cc-best:xxx). Clone users: run convert-to-local.js.

Setup Demo

git clone https://github.com/xiaobei930/cc-best.git .claude
cd .claude && bash scripts/shell/init.sh
# Convert command format from /cc-best:xxx to /xxx
node scripts/node/convert-to-local.js

# Remove the plugin
/plugin uninstall cc-best@xiaobei930
# Remove marketplace (optional)
/plugin marketplace remove xiaobei930/cc-best

After running /cc-best:iterate "implement user authentication", Claude will:

1. 📋 /cc-best:pm → Analyze requirements, create task breakdown
2. 🏗️ /cc-best:lead → Design technical solution
3. 💻 /cc-best:dev → Write code, create tests
4. 🧪 /cc-best:qa → Run tests, verify quality
5. ✅ /cc-best:commit → Commit changes with proper message

You just watch. Intervene only when needed.

While CC-Best is built for Claude Code, the methodology (Dao-Fa-Shu-Qi) and role-driven patterns are framework-agnostic and can be adapted for other AI coding assistants.

Read progress.md → Select role → Execute → Verify → Commit → Next task (no waiting)

observe → analyze → learn → evolve

your-project/
├── CLAUDE.md # Project constitution
├── commands/ # 44 slash commands
├── skills/ # 19 development skills
├── agents/ # 8 specialized agents
├── rules/ # 43 coding standards (10 dirs)
├── hooks/ # Safety hooks
├── scripts/ # Automation (node/python/shell)
├── memory-bank/ # Progress & architecture docs
└── .claude/ # Claude Code config

flowchart LR
 PM["/pm<br/>Requirements"] --> Clarify["/clarify<br/>Clarify"]
 Clarify --> Lead["/lead<br/>Design"]
 Lead --> Designer["/designer<br/>UI Design"]
 Designer --> Dev["/dev<br/>Implement"]
 Dev --> QA["/qa<br/>Test"]
 QA --> Verify["/verify<br/>Verify"]
 Verify --> Commit["/commit<br/>Commit"]
 Commit --> Clear["/clear<br/>Clear Context"]
 Clear -.->|Loop| PM

📖 Detailed usage guide: See MODES.md for comprehensive documentation on each mode, including when to use, how to control, and best practices.

44 commands organized into categories:

📖 Full reference: See COMMANDS.md for all parameters and usage examples.

19 development skills organized by domain:

📖 Full reference: See skills/README for detailed skill documentation.

CC-Best uses a four-tier architecture:

flowchart TB
 subgraph User["👤 You"]
 CMD["/cc-best:iterate 'add feature'"]
 end
 subgraph Commands["📋 Commands (44)"]
 PM["/pm"] --> Lead["/lead"] --> Dev["/dev"] --> QA["/qa"]
 end
 subgraph Skills["🛠️ Skills (19)"]
 S1["backend · frontend · testing · security"]
 S2["architecture · devops · git"]
 S3["learning · compact · exploration"]
 end
 subgraph Agents["🤖 Agents (8)"]
 A1["architect · planner · code-reviewer"]
 A2["code-simplifier · security-reviewer"]
 A3["tdd-guide · build-error-resolver · requirement-validator"]
 end
 subgraph Safety["🛡️ Safety Hooks (30)"]
 H1["PreToolUse: validate, secrets, protect"]
 H2["PostToolUse: format, typecheck, observe"]
 end
 CMD --> Commands
 Commands -.->|"auto-inject"| Skills
 Commands -.->|"delegate"| Agents
 Commands -.->|"guard"| Safety

8 specialized agents: architect, build-error-resolver, code-reviewer, code-simplifier, planner, requirement-validator, security-reviewer, tdd-guide

📐 Full documentation: See ARCHITECTURE.md for component relationships and call chains.

🤖 Agent details: See agents/README for agent capabilities and invocation.

CC-Best is designed to work seamlessly with official Claude Code plugins. Our built-in agents and skills complement (not replace) official plugins.

{
 "enabledPlugins": {
 "code-review@claude-plugins-official": true,
 "hookify@claude-plugins-official": true,
 "security-guidance@claude-plugins-official": true
 }
}

• No plugins installed: Built-in agents/skills work standalone
• With plugins: Use official plugins for advanced features, CC-Best for quick local checks
• Best practice: Install official plugins, use built-in agents for immediate feedback, official plugins for deep analysis

Create a file in rules/:

---
paths:
 - "**/*.your-ext"
---
# Rule Title
## Rule Content
...

Create a file in commands/:

---
allowed_tools:
 - Read
 - Edit
 - Write
 - Bash
---
# /your-command - Command Name
## Responsibilities
...
## Execution Steps
1. ...
2. ...

Edit .claude/settings.local.json:

{
 "hooks": {
 "PreToolUse": [
 {
 "matcher": "Bash",
 "hooks": [
 {
 "type": "command",
 "command": "python scripts/your-script.py",
 "timeout": 5
 }
 ]
 }
 ]
 }
}

⚠️ Important: Hooks Require Manual Setup

Due to a known Claude Code issue, plugin hooks are disabled by default. To enable the safety guards and automation hooks, run:

/cc-best:setup --hooks

This command configures hooks with absolute paths. See the FAQ for more details.

All hooks default to Node.js for cross-platform compatibility. Python/Bash alternatives available in scripts/.

• Keep it under 100 lines
• Put detailed specifications in rules/

• Update progress.md after each task completion
• Record important decisions in architecture.md

• Normal mode: Use /clear frequently to avoid context overflow
• /cc-best:iterate mode: Don't clear manually, maintain loop continuity

• Enable no more than 10 MCP servers per project
• Use disabledMcpServers to disable unused ones

• Delete unused language rules
• Remove unused commands

MCP tools auto-create temporary directories in your project:

Cleanup Script: Use cleanup.sh for regular maintenance:

# Preview files to delete (dry run)
bash scripts/shell/cleanup.sh --dry-run
# Clean files older than 7 days (default)
bash scripts/shell/cleanup.sh
# Clean files older than 3 days
bash scripts/shell/cleanup.sh --days 3
# Clean all MCP temporary files
bash scripts/shell/cleanup.sh --all

📖 Full FAQ: See FAQ.md for comprehensive troubleshooting guides.

{ "enabledMcpjsonServers": ["memory", "sequential-thinking"] }

Some commands use MCP (Model Context Protocol) tools for enhanced functionality:

Note: These are optional. Commands work without MCP servers but with reduced functionality. Install via Claude Code settings: Settings > MCP Servers

• Anthropic Official Best Practices
• CLAUDE.md Complete Guide

• Quick Start Guide - Get started in 5 minutes
• Advanced Guide - Deep dive into methodology and architecture

CC-Best's internal files (commands/, rules/, skills/) are written in Chinese. This is intentional:

• Claude understands Chinese - All Claude models can read and follow Chinese instructions perfectly
• No translation burden - Maintaining dual-language internal files would be impractical
• Focus on users - The README (this file) is fully English for international users

If you prefer English internal files, community contributions for English translations are welcome!

Contributions are welcome! See CONTRIBUTING.md for details.

MIT License - Free to use and modify

🌐 Visit Homepage · ⭐ Star on GitHub

If CC-Best helps you, please give it a ⭐ Star!

Star History Chart