Preview — full styling will appear after the next deploy completes.

bmad-method

BMAD vs SpecOps

When to use each, when to combine them

BMAD and SpecOps are complementary methodologies for AI-driven development. BMAD structures the process; SpecOps structures the output. The right choice depends on how well-understood requirements are when work begins.

flowchart TD
    RQ([Requirements]) --> CQ{How well<br>understood?}
    CQ -->|Emerging or unclear| BM[BMAD<br>Persona workflow<br>clarifies requirements]
    CQ -->|Clear and stable| SO[SpecOps<br>Tight spec first<br>then implement]
    CQ -->|Partially clear| HB[Hybrid<br>BMAD to draft spec<br>SpecOps to tighten it]
    BM --> IM([Implementation])
    SO --> IM
    HB --> IM

BMAD and SpecOps address the same fundamental problem — getting consistent, production-quality output from AI coding tools — from different directions. BMAD structures the process: it tells you which persona to activate, what artifact to produce, and what the handoff looks like. SpecOps structures the output: it tells you to write a tight specification first, then hand that specification to the AI for implementation. Both work. Neither works for everything.

BMAD fits better when requirements are still emerging. The persona workflow is designed to help you figure out what you're building as you go — the BA clarifies the problem, the PM shapes the stories, and the Architect constrains the design. Each phase produces a reviewable artifact that can be revised before the next phase begins. SpecOps fits better when requirements are already clear. If you can write a complete, unambiguous spec without guessing, the upfront investment pays off — the AI either satisfies the contract or it doesn't. Applying SpecOps to exploratory work produces false confidence.

In practice, BMAD and SpecOps compose well. A common pattern is to use BMAD's persona workflow to produce a draft specification, then apply SpecOps discipline to tighten it before implementation begins. The BA and PM phases produce the raw material; SpecOps rigour shapes it into a tight contract. This hybrid captures BMAD's flexibility for the uncertain parts and SpecOps' rigour for the parts that are well understood.