Specs & Workflow
A spec is the unit of work. It lives in .mm/specs/{date-slug}/spec.md with its goal, requirements, and tasks in one file.
The lifecycle
Section titled “The lifecycle”| Stage | What happens | How |
|---|---|---|
| Brief | The request, captured with the milestone it serves | Prompt bar → Accept & queue, or /mm:spec |
| Shape | An agent writes requirements (R1, R2…) and a task list citing them | shape now, or /mm:spec --stage brief |
| Implement | An agent works the tasks in its own worktree, committing per task | start, or /mm:spec-start |
| Verify | The implementation is graded against each requirement | /mm:verify-spec — runs automatically at the end of a run |
| Done | Only a passing verdict (or your override) sets status: done | — |
| Land | The worktree merges to main | push to main |
On the board
Section titled “On the board”A spec is a card in the Specs column. It expands in place to show its tasks or its brief, carries its running session, and offers the verb it’s ready for. Questions from its agent appear in Inbox.
Ordering
Section titled “Ordering”depends_on: lists the specs that must finish first. /mm:order-specs computes the build order; a spec waiting on an unfinished prerequisite reads as blocked.