mirror of
https://github.com/cexll/myclaude.git
synced 2026-02-05 02:30:26 +08:00
5a50131a13
- Create agents/ directory, move bmad, requirements, development-essentials - Remove docs/, hooks/, dev-workflow/ directories - Add npx support via github:cexll/myclaude - Add bin/cli.js with --update command for installed modules - Add package.json, skills/README.md, PLUGIN_README.md - Update all references across config.json, README, marketplace.json - Change default module from dev to do - Update CHANGELOG with all 59 tags BREAKING CHANGE: Directory structure changed, docs/hooks removed Generated with SWE-Agent.ai Co-Authored-By: SWE-Agent.ai <noreply@swe-agent.ai>
bmad - BMAD Agile Workflow
Full enterprise agile methodology with 6 specialized agents, UltraThink analysis, and repository-aware development.
Installation
python install.py --module bmad
Usage
/bmad-pilot <PROJECT_DESCRIPTION> [OPTIONS]
Options
| Option | Description |
|---|---|
--skip-tests |
Skip QA testing phase |
--direct-dev |
Skip SM planning, go directly to development |
--skip-scan |
Skip initial repository scanning |
Workflow Phases
| Phase | Agent | Deliverable | Description |
|---|---|---|---|
| 0 | Orchestrator | 00-repo-scan.md |
Repository scanning with UltraThink analysis |
| 1 | Product Owner (PO) | 01-product-requirements.md |
PRD with 90+ quality score required |
| 2 | Architect | 02-system-architecture.md |
Technical design with 90+ score required |
| 3 | Scrum Master (SM) | 03-sprint-plan.md |
Sprint backlog with stories and estimates |
| 4 | Developer | Implementation code | Multi-sprint implementation |
| 4.5 | Reviewer | 04-dev-reviewed.md |
Code review (Pass/Pass with Risk/Fail) |
| 5 | QA Engineer | Test suite | Comprehensive testing and validation |
Agents
| Agent | Role |
|---|---|
bmad-orchestrator |
Repository scanning, workflow coordination |
bmad-po |
Requirements gathering, PRD creation |
bmad-architect |
System design, technology decisions |
bmad-sm |
Sprint planning, task breakdown |
bmad-dev |
Code implementation |
bmad-review |
Code review, quality assessment |
bmad-qa |
Testing, validation |
Approval Gates
Two mandatory stop points require explicit user approval:
- After PRD (Phase 1 → 2): User must approve requirements before architecture
- After Architecture (Phase 2 → 3): User must approve design before implementation
Output Structure
.claude/specs/{feature_name}/
├── 00-repo-scan.md
├── 01-product-requirements.md
├── 02-system-architecture.md
├── 03-sprint-plan.md
└── 04-dev-reviewed.md
UltraThink Methodology
Applied throughout the workflow for deep analysis:
- Hypothesis Generation - Form hypotheses about the problem
- Evidence Collection - Gather evidence from codebase
- Pattern Recognition - Identify recurring patterns
- Synthesis - Create comprehensive understanding
- Validation - Cross-check findings
Interactive Confirmation Flow
PO and Architect phases use iterative refinement:
- Agent produces initial draft + quality score
- Orchestrator presents to user with clarification questions
- User provides responses
- Agent refines until quality >= 90
- User confirms to save deliverable
When to Use
- Large multi-sprint features
- Enterprise projects requiring documentation
- Team coordination scenarios
- Projects needing formal approval gates
Directory Structure
agents/bmad/
├── README.md
├── commands/
│ └── bmad-pilot.md
└── agents/
├── bmad-orchestrator.md
├── bmad-po.md
├── bmad-architect.md
├── bmad-sm.md
├── bmad-dev.md
├── bmad-review.md
└── bmad-qa.md