skills/bmad-orchestrator/SKILL.md
Orchestrates BMAD workflows for structured AI-driven development. Routes work across Analysis, Planning, Solutioning, and Implementation phases.
npx skillsauth add jyjeanne/ai-setup-forge bmad-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
npx skills add https://github.com/supercent-io/skills-template --skill bmad-orchestrator
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 phase routing should be treated with the same three-layer abstraction used by JEO:
settings: platform-specific runtime configuration such as Claude hooks, Codex/Gemini instructions, and MCP setuprules: phase constraints such as "do not advance before the current phase document is approved" and "do not reopen the same unchanged phase document for review"hooks: platform callbacks such as Claude ExitPlanMode, Codex notify, or Gemini AfterAgentFor BMAD phase gates, the intended rule is strict:
| 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:
Use these in your AI session:
/workflow-init
/workflow-status
Typical flow:
/workflow-init to bootstrap BMAD config./workflow-status any time to inspect current phase and progress.| Action | Command |
|--------|---------|
| Initialize BMAD | /workflow-init |
| Check BMAD status | /workflow-status |
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.
[[BMAD Plans]] backlinkAfter 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 open the plannotator UI for review. In Claude Code: call EnterPlanMode → write plan → call ExitPlanMode (hook fires automatically). In OpenCode: the submit_plan plugin tool is available directly.
/prd completes → docs/prd-myapp.md created
↓
bash scripts/phase-gate-review.sh docs/prd-myapp.md
↓
hash guard checks whether this exact document was already reviewed
↓
unchanged hash? yes → keep previous terminal result, do not reopen UI
↓ no
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)
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
...
| 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 |
development
Generate breadboard circuit mockups and visual diagrams using HTML5 Canvas drawing techniques. Use when asked to create circuit layouts, visualize electronic component placements, draw breadboard diagrams, mockup 6502 builds, generate retro computer schematics, or design vintage electronics projects. Supports 555 timers, W65C02S microprocessors, 28C256 EEPROMs, W65C22 VIA chips, 7400-series logic gates, LEDs, resistors, capacitors, switches, buttons, crystals, and wires.
development
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "UX experiment", "collaborative design", or "outcome over output". Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.
development
Design MVPs, validated learning experiments, and pivot-or-persevere decisions using Build-Measure-Learn. Use when the user mentions "MVP scope", "validated learning", "pivot or persevere", "vanity metrics", or "test assumptions". Covers innovation accounting and actionable metrics. For 5-day prototype testing, see design-sprint. For customer motivation analysis, see jobs-to-be-done.
tools
Instrument, trace, evaluate, and monitor LLM applications and AI agents with LangSmith. Use when setting up observability for LLM pipelines, running offline or online evaluations, managing prompts in the Prompt Hub, creating datasets for regression testing, or deploying agent servers. Triggers on: langsmith, langchain tracing, llm tracing, llm observability, llm evaluation, trace llm calls, @traceable, wrap_openai, langsmith evaluate, langsmith dataset, langsmith feedback, langsmith prompt hub, langsmith project, llm monitoring, llm debugging, llm quality, openevals, langsmith cli, langsmith experiment, annotate llm, llm judge.