Spec-driven development

For large or regulated products, where the requirements are written down first and traceability matters. You plan fully with BMad; madcompany imports the stories, anchors every requirement ID so it's clickable, and the team builds epic by epic.

Plan with: full BMad planning: brief, PRD, UX spec, architecture, and epics with stories.

Delivery

Each epicEpic by epic

Stories become tickets. Each epic ends with a demo; once you approve, its branch goes to main.

Steps

Terminal
npx madcompany init --mode spec
Set up, then keep npx madcompany hq running
Claude Code
/bmad-product-brief
The product brief
Claude Code
/bmad-prd
Requirements (FR/NFR), all clickable later
Claude Code
/bmad-ux
The UX design
Claude Code
/bmad-architecture
The architecture
Claude Code
/bmad-create-epics-and-stories
Epics and stories
Claude Code
/mc-staff
Pick the team, then restart Claude Code once
Claude Code
/mc-plan-epic
Import the stories as tickets, anchor every ID
Claude Code
/mc-ui-sprint
For epics with screens
Claude Code
/mc-start
The team builds the epic; approve it in HQ → Epics
Terminal
npx madcompany ship E1
Merge into main and tag; push and deploy are in Human help

What the import does

/mc-plan-epic runs npx madcompany import, which:

adds a stable anchor to every FR, NFR, epic and story definition in your BMad docs (<a id="fr12"></a>), so FR12 anywhere in HQ opens that exact line
links bare references like "FR12" that should be links (npx madcompany refs check and refs fix do the same any time)
creates one ticket per story, with its "Depends on" lines as dependencies

The lead then splits each story into single-domain tickets: design packs first, UI on mock data, then backend and integration. Every ticket keeps its refs, so you can trace any line of code back to a requirement.

You and the team

You

Plan with BMad's agents
Sit in a UI sprint for epics with screens
Answer the questions that reach your Inbox
Approve each epic at its demo in HQ → Epics
Do the Human help items

The team

Imports and splits the stories
Builds against agreed contracts, UI first
Links every reference it writes
Merges into epic/N through the merge queue; npx madcompany ship E1 takes an approved epic to main

Tips

If your epics file isn't in _bmad-output/planning-artifacts/, pass it: npx madcompany import --epics path/to/epics.md.
BMad skill names change between versions. If one of the commands above doesn't exist in yours, /bmad-help lists the current ones.