Agent skill
bmad-orchestrator
Orchestrates BMAD workflows for structured AI-driven development. Routes work across Analysis, Planning, Solutioning, and Implementation phases.
Install this agent skill to your Project
npx add-skill https://github.com/autohandai/community-skills/tree/main/bmad-orchestrator
Metadata
Additional technical details for this skill
- tags
- bmad, orchestrator, workflow, planning, implementation
- source
- user-installed skill
- keyword
- bmad
- version
- 1.1.0
- platforms
- Claude, Gemini, Codex, OpenCode
SKILL.md
bmad-orchestrator - BMAD Workflow Orchestration
When to use this skill
- Initializing BMAD in a new project
- Checking and resuming BMAD workflow status
- Routing work across Analysis, Planning, Solutioning, and Implementation
- Managing structured handoff between phases
Installation
npx skills add https://github.com/supercent-io/skills-template --skill bmad-orchestrator
Notes for Codex Usage
bmad-orchestrator's default execution path is Claude Code.
To run the same flow directly in Codex, we recommend operating BMAD stages via a higher-level orchestration path such as omx/ohmg.
BMAD Execution Commands
Platform Support Status (Current)
| Platform | Current support mode | Requirements |
|---|---|---|
| Gemini CLI | Native (recommended) | Register the bmad keyword, then run /workflow-init |
| Claude Code | Native (recommended) | Install skill + remember pattern |
| OpenCode | Orchestration integration | Use an omx/ohmg/omx-style bridge |
| Codex | Orchestration integration | Use an omx/ohmg-style bridge |
Possible with this skill alone:
- Gemini CLI/Claude Code: Yes
- OpenCode/Codex: Yes (via orchestration)
Use these in your AI session:
/workflow-init
/workflow-status
Typical flow:
- Run
/workflow-initto bootstrap BMAD config. - Move through phases in order: Analysis -> Planning -> Solutioning -> Implementation.
- Run
/workflow-statusany time to inspect current phase and progress.
Quick Reference
| Action | Command |
|---|---|
| Initialize BMAD | /workflow-init |
| Check BMAD status | /workflow-status |
plannotator Integration (Phase Review Gate)
Each BMAD phase produces a key document (PRD, Tech Spec, Architecture). Before transitioning to the next phase, review that document with plannotator and auto-save it to Obsidian.
Why use plannotator with BMAD?
- Quality gate: Approve or request changes before locking in a phase deliverable
- Obsidian archive: Every approved phase document auto-saves with YAML frontmatter and
[[BMAD Plans]]backlink - Team visibility: Share a plannotator link so stakeholders can annotate the PRD/Architecture before implementation begins
Phase Review Pattern
After completing any phase document, submit it for review:
# After /prd → docs/prd-myapp-2026-02-22.md is created
bash scripts/phase-gate-review.sh docs/prd-myapp-2026-02-22.md "PRD Review: myapp"
# After /architecture → docs/architecture-myapp-2026-02-22.md is created
bash scripts/phase-gate-review.sh docs/architecture-myapp-2026-02-22.md "Architecture Review: myapp"
Or submit the plan directly from within your AI session:
# In Claude Code after /prd completes:
planno — review the PRD before we proceed to Phase 3
The agent will call submit_plan with the document content, opening the plannotator UI for review.
Phase Gate Flow
/prd completes → docs/prd-myapp.md created
↓
bash scripts/phase-gate-review.sh docs/prd-myapp.md
↓
plannotator UI opens in browser
↓
[Approve] [Request Changes]
↓ ↓
Obsidian saved Agent revises doc
bmm-workflow-status Re-submit for review
updated automatically
↓
/architecture (Phase 3)
Obsidian Save Format
Approved phase documents are saved to your Obsidian vault with:
---
created: 2026-02-22T22:45:30.000Z
source: plannotator
tags: [bmad, phase-2, prd, myapp]
---
[[BMAD Plans]]
# PRD: myapp
...
Quick Reference
| Phase | Document | Gate Command |
|---|---|---|
| Phase 1 → 2 | Product Brief | bash scripts/phase-gate-review.sh docs/product-brief-*.md |
| Phase 2 → 3 | PRD / Tech Spec | bash scripts/phase-gate-review.sh docs/prd-*.md |
| Phase 3 → 4 | Architecture | bash scripts/phase-gate-review.sh docs/architecture-*.md |
| Phase 4 done | Sprint Plan | bash scripts/phase-gate-review.sh docs/sprint-status.yaml |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
mapping-mitre-attack-techniques
Maps observed adversary behaviors, security alerts, and detection rules to MITRE ATT&CK techniques and sub-techniques to quantify detection coverage and guide control prioritization. Use when building an ATT&CK-based coverage heatmap, tagging SIEM alerts with technique IDs, aligning security controls to adversary playbooks, or reporting threat exposure to executives. Activates for requests involving ATT&CK Navigator, Sigma rules, MITRE D3FEND, or coverage gap analysis.
hunting-for-spearphishing-indicators
Hunt for spearphishing campaign indicators across email logs, endpoint telemetry, and network data to detect targeted email attacks.
analyzing-malicious-url-with-urlscan
URLScan.io is a free service for scanning and analyzing suspicious URLs. It captures screenshots, DOM content, HTTP transactions, JavaScript behavior, and network connections of web pages in an isolat
implementing-zero-standing-privilege-with-cyberark
Deploy CyberArk Secure Cloud Access to eliminate standing privileges in hybrid and multi-cloud environments using just-in-time access with time, entitlement, and approval controls.
implementing-pam-for-database-access
Deploy privileged access management for database systems including Oracle, SQL Server, PostgreSQL, and MySQL. Covers session proxy configuration, credential vaulting, query auditing, dynamic credentia
detecting-t1003-credential-dumping-with-edr
Detect OS credential dumping techniques targeting LSASS memory, SAM database, NTDS.dit, and cached credentials using EDR telemetry, Sysmon process access monitoring, and Windows security event correlation.
Didn't find tool you were looking for?