mm_order_specs
Compute deterministic spec ordering (topological waves, cycle detection, file-overlap parallelism) from depends_on frontmatter across all specs. Call with just project_path for read-only analysis, or write: true (optionally with labels, a map of phase -> {label, reasons}) to have the tool write .mm/specs/order.json itself — waves and overlaps are always this tool’s own computation, never derived from labels.
At a Glance
Section titled “At a Glance”- Category: Core
- Source: Built-in
- Availability: Listed by default
- Required parameters: 1
- Total parameters: 3
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
project_path | string | Yes | Absolute path to the project root |
write | boolean | No | |
labels | object | No |
Example
Section titled “Example”{ "tool": "mm_order_specs", "arguments": { "project_path": "/Users/you/projects/my-app", "write": true, "labels": {} }}Related Tools
Section titled “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…