Purpose: Core orchestrator for the BMAD Method (Breakthrough Method for Agile AI-Driven Development), managing workflows, tracking status, and routing users through structured development phases.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbmad-orchestratorExecute the skills CLI command in your project's root directory to begin installation:
Fetches bmad-orchestrator from aj-geddes/claude-code-bmad-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate bmad-orchestrator. Access via /bmad-orchestrator in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
365
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
365
stars
Purpose: Core orchestrator for the BMAD Method (Breakthrough Method for Agile AI-Driven Development), managing workflows, tracking status, and routing users through structured development phases.
Use this skill when:
/workflow-init or /init - Initialize BMAD in a project/workflow-status or /status - Check progress and get recommendationsPlanning Requirements by Level:
Initialize BMAD structure in the current project.
Steps:
Create directory structure:
bmad/
├── config.yaml
└── agent-overrides/
docs/
├── bmm-workflow-status.yaml
└── stories/
.claude/commands/bmad/ (if not exists)
Collect project information:
Create project config using config.template.yaml
Create workflow status file with conditional requirements based on level:
Display initialization summary and recommend next workflow
Offer to start recommended workflow
Example interaction:
User: /workflow-init
Orchestrator: I'll initialize BMAD for your project.
[Collects info, creates files...]
✓ BMAD Method initialized!
Project: MyApp
Type: web-app
Level: 2 (Medium feature set)
Configuration: bmad/config.yaml
Status tracking: docs/bmm-workflow-status.yaml
Recommended next step: Create Product Brief with /product-brief
This will help define your product vision and requirements.
Would you like to start with /product-brief?
Check project status and get recommendations for next steps.
Steps:
Status Indicators:
Example interaction:
User: /status
Orchestrator: Checking your project status...
Project: MyApp (Web Application, Level 2)
✓ Phase 1: Analysis
✓ product-brief (docs/product-brief-myapp-2025-01-11.md)
→ Phase 2: Planning [CURRENT]
⚠ prd (required - NOT STARTED)
- tech-spec (optional)
Phase 3: Solutioning
- architecture (required)
Phase 4: Implementation
- sprint-planning (required)
Recommended next step: Create PRD with /prd command
Would you like to run /prd to create your PRD?
If project not initialized:
/workflow-initAfter determining project status, route users to specialized workflows:
/product-brief, /brainstorm, /research/prd, /tech-spec/create-ux-design/architecture/sprint-planning, /create-story/dev-story, /code-reviewRecommendation logic:
/product-brief/tech-spec/prd/architecture/sprint-planning/create-story or /dev-storySee REFERENCE.md for detailed routing logic.
project_name: "MyApp"
project_type: "web-app" # web-app, mobile-app, api, game, library, other
project_level: 2 # 0-4
output_folder: "docs"
communication_language: "English"
Tracks completion of each workflow with status values:
"optional" - Can be skipped"recommended" - Strongly suggested"required" - Must be completed"{file-path}" - Completed (shows output file)"skipped" - Explicitly skippedSee templates/config.template.yaml for full template.
Execute via Bash tool:
init-project.sh - Automated project initialization
bash scripts/init-project.sh --name "MyApp" --type web-app --level 2
check-status.sh - Display current workflow status
bash scripts/check-status.sh
validate-config.sh - Validate YAML configuration
bash scripts/validate-config.sh bmad/config.yaml
See scripts documentation for details.
Config missing:
/workflow-initInvalid YAML:
Template missing:
Status file inconsistent:
This orchestrator coordinates with specialized BMAD skills:
business-analyst - Analysis phase workflowsproduct-manager - Planning phase workflowssystem-architect - Architecture designscrum-master - Sprint and story managementdeveloper - Development workflowsWhen routing to these skills, pass context:
This skill leverages parallel subagents to maximize context utilization (each agent has up to 1M tokens on Claude Sonnet 4.6 / Opus 4.6).
Pattern: Fan-Out Research Agents: 3-4 parallel agents
| Agent | Task | Output |
|---|---|---|
| Agent 1 | Check project config and validate structure | bmad/outputs/config-status.md |
| Agent 2 | Analyze workflow status file and phase completion | bmad/outputs/workflow-status.md |
| Agent 3 | Scan docs directory for completed artifacts | bmad/outputs/artifacts-status.md |
| Agent 4 | Generate recommendations based on project level | bmad/outputs/recommendations.md |
Coordination:
Pattern: Parallel Section Generation Agents: 3 parallel agents
| Agent | Task | Output |
|---|---|---|
| Agent 1 | Create directory structure and validate paths | bmad/outputs/directory-setup.md |
| Agent 2 | Generate project config from template | bmad/config.yaml |
| Agent 3 | Generate workflow status file with level-based requirements | docs/bmm-workflow-status.yaml |
Coordination:
Task: Analyze workflow status and determine current phase
Context: Read bmad/config.yaml and docs/bmm-workflow-status.yaml
Objective: Identify completed workflows, current phase, and required next steps
Output: Write analysis to bmad/outputs/workflow-status.md
Deliverables:
1. List of completed workflows with file paths
2. Current phase determination
3. Required vs optional next workflows
4. Blocking issues or missing dependencies
Constraints:
- Use project level to determine requirements
- Flag any inconsistencies in status file
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
bmad-orchestrator has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: bmad-orchestrator is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: bmad-orchestrator is the kind of skill you can hand to a new teammate without a long onboarding doc.
bmad-orchestrator has been reliable in day-to-day use. Documentation quality is above average for community skills.
bmad-orchestrator has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: bmad-orchestrator is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend bmad-orchestrator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in bmad-orchestrator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in bmad-orchestrator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend bmad-orchestrator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 39