ApiHug BMAD

Use ApiHug BMAD to connect requirements, proto design, implementation, and review through AI workflows.

ApiHug BMAD applies BMAD-style AI delivery to the ApiHug stack. It is the workflow layer that connects requirements, protobuf contracts, implementation, and review.

What It Is

ApiHug BMAD combines:

workflow entry points for recurring delivery jobs
agents that understand ApiHug conventions
a REPL-based install and update path

Why It Matters

Generic AI workflows do not know where ApiHug contracts live, which layers are generated, or which rules reviewers must enforce. BMAD adds that project-specific context.

Install It

BMAD depends on ApiHug REPL.

Terminal

./apihug
apihug> install

Common install options:

Terminal

install --directory ~/projects/my-api --ides cursor
install --quick-update true
install --compile-agents true

How It Fits

Core workflows

Workflow path	Primary use
`/bmad:bmw:workflows:apihug-proto-design`	generate or refine protobuf contracts
`/bmad:bmw:workflows:apihug-end-to-end`	run a requirement-to-code flow
`/bmad:bmw:workflows:apihug-project-review`	review a project against ApiHug rules
`/bmad:bmw:workflows:apihug-app-implement`	implement application logic from a prepared contract

Core agent

/bmad:bmw:agents:apihug is the interactive agent surface for ApiHug-specific drafting and review.

Best-fit usage

choose apihug-proto-design when the main job is contract design
choose apihug-end-to-end when the story spans contract and code
choose apihug-project-review when you need a rule-based audit
choose apihug-app-implement when the contract is ready and the job is handwritten logic

Next Step

Install or update through ApiHug REPL
Pair BMAD with Skills & Rules so the workflow stays aligned with ApiHug boundaries