mm_order_specs

Deterministic spec ordering: reads all specs, parses depends_on frontmatter, runs topological sort into waves, detects cycles, and checks file overlaps for parallelism (file overlap detection falls back to scraping paths out of task text when a spec has no manifest.md). Waves, parallel, and file_overlaps are always this tool’s own deterministic computation — never derived from a labels argument. Call with just project_path for read-only analysis. Pass write: true (optionally with labels, a map of phase-number-string -> {label, reasons: {spec-slug: reason}}) to have the tool write .mm/specs/order.json itself — the model supplies only label/reason prose, never the ordering data.

At a Glance

• Category: Core
• Source: Built-in
• Availability: Listed by default
• Required parameters: 1
• Total parameters: 3

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root
write	boolean	No	When true, write the deterministic result to .mm/specs/order.json.
labels	object	No	Optional per-phase label/reason strings keyed by phase number as a string (e.g. ‘1’). Each value is {label?: string, reasons?: {spec-slug: reason}}. Missing entries get deterministic defaults (‘Wave N’, a dependency-derived reason). Only used when write is true.

Example

{
  "tool": "mm_order_specs",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "write": true,
    "labels": {}
  }
}

Related Tools

• mm_search - Full-text search across all entity types (specs, features, issues, notes, ide…
• mm_configure_integration - Configure an external service integration (github, trello, grain, gmail, noti…
• mm_sync_notion - Bidirectional sync between a Notion database and .mm/specs/ or .mm/notes/. Pu…
• mm_daily_brief - Generate a structured morning summary with active tasks, blockers, recently c…
• mm_revert_spec_completion - Revert a spec’s completion status in its parent feature. Tasks stay [x] but t…