Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Orchestrate the full BMAD Method workflow across OpenClaw and Claude Code. Use when starting a new project with BMAD methodology, running BMAD phases (brains...
Orchestrate the full BMAD Method workflow across OpenClaw and Claude Code. Use when starting a new project with BMAD methodology, running BMAD phases (brains...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Orchestrate the 4-phase BMAD Method (Breakthrough Method of Agile AI Driven Development) across OpenClaw β Claude Code.
Phases 1-3 (Interactive): Run through OpenClaw chat with the user. You facilitate brainstorming, refine the PRD, debate architecture. The user's ideas matter most here. Party Mode: At key decision points, suggest running party mode on Claude Code β multiple BMAD agents debate the topic and produce richer output. Phase 4 (Automated): Delegate to Claude Code via tmux on the dev VM. Monitor progress, report back.
Claude Code installed on dev VM (accessible via SSH) BMAD framework installed in the project (_bmad/ directory with agents, workflows, commands) tmux available on the dev VM
Track workflow state in _bmad-output/orchestrator-state.yaml: project: <name> vm_host: <ip> vm_user: <user> project_path: <path> tmux_socket: /tmp/openclaw-tmux-sockets/openclaw.sock tmux_session: bmad-<project> current_phase: 1|2|3|4 current_workflow: <workflow-name> artifacts: brainstorming_report: null|path product_brief: null|path prd: null|path ux_spec: null|path architecture: null|path epics: null|path sprint_status: null|path project_context: null|path
Run this conversationally with the user in OpenClaw chat: Ask: "What project are we building? Give me the elevator pitch." Explore the problem space β ask about users, pain points, existing solutions Challenge assumptions β play devil's advocate Suggest Party Mode: "Want me to run party mode on Claude Code? The BMAD agents (analyst, architect, PM, dev) will debate your idea and surface things we might miss." If party mode β send /bmad-brainstorming to Claude Code, capture output, share highlights Synthesize into key decisions and themes Produce: brainstorming-report.md
If the project needs market/technical/domain validation: Discuss with user what needs validation Send research workflow to Claude Code for heavy lifting Review findings together
Start from brainstorming output Walk through with user: vision, target users, success metrics, scope Suggest Party Mode: "The PM and analyst agents can stress-test this brief. Run it?" If party mode β send command, capture debate highlights Iterate until user approves Produce: product-brief.md
Load product brief as context Walk through requirements with user section by section: Functional requirements (FRs) Non-functional requirements (NFRs) User journeys Success metrics Suggest Party Mode: "PM + architect + QA can review these requirements together. Good time to catch gaps." If party mode β send command, share findings Iterate until user signs off Produce: prd.md
Only for projects with UI. Skip for backend/infrastructure tools.
Load PRD as context Discuss technical decisions with user: Language/framework choices Deployment model Key patterns and trade-offs ADRs (Architecture Decision Records) Suggest Party Mode: "Architect + dev + QA debating the architecture will surface implementation risks early." If party mode β send command, share the debate Iterate with user Produce: architecture.md with ADRs
Load architecture + PRD Present epic breakdown to user for review Discuss story sizing, priorities, dependencies Produce: epics.md with stories
Send to Claude Code for automated gate check Share result: PASS / CONCERNS / FAIL If CONCERNS/FAIL β discuss with user, fix gaps Produce: readiness report
Send to Claude Code after architecture is finalized Review output with user Produce: project-context.md
See references/tmux-setup.md for tmux session initialization.
Send to Claude Code: /bmad-bmm-sprint-planning Capture and save sprint-status.yaml.
For each epic, for each story: Create Story: Send /bmad-bmm-create-story β produces story-[slug].md Dev Story: Send /bmad-bmm-dev-story β implements code + tests Code Review: Send /bmad-bmm-code-review β validates quality If review fails β send fixes back, re-review Update sprint status Commit after each story
After all stories in an epic: Send /bmad-bmm-retrospective for lessons learned Optionally run /bmad-bmm-automate for E2E test generation Commit and update sprint status
Set up a cron job to monitor Claude Code progress every 15 minutes. Report status updates to user via chat.
Party mode simulates a multi-agent discussion in Claude Code. Use it at these moments: WhenWhyCommandAfter brainstormingSurface blind spots/bmad-party-mode with brainstorming contextAfter product briefStress-test the vision/bmad-party-mode with briefDuring PRD reviewCatch requirement gaps/bmad-party-mode with PRD draftArchitecture decisionsDebate trade-offs/bmad-party-mode with architecture To trigger party mode on Claude Code: tmux send-keys -l -- "/bmad-party-mode" && sleep 0.3 && tmux send-keys Enter Capture output, extract key insights, present to user.
See references/bmad-commands.md for the full command list.
For small, well-understood work: /bmad-bmm-quick-spec β tech-spec.md /bmad-bmm-quick-dev β implementation Only use when user explicitly says the project is simple and well-understood.
See references/tmux-setup.md for the tmux interaction patterns. Key rules: Split text and Enter with a delay (Claude Code TUI timing) Use capture-pane -S -200 to read output Wait for idle prompt before sending next command Use C-c to interrupt if stuck
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.