mm_retrieve_prior_work

Regenerate prior-work.md for an existing spec by re-running similarity retrieval against the current spec index at .mm/index/specs.json. Idempotent — running twice on the same inputs produces a byte-identical file (the generated_at timestamp is preserved when the body is unchanged). When no completed specs match above the configured similarity_threshold, writes the empty-state file with a clear empty_reason.

At a Glance

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

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root
spec_path	string	Yes	Spec folder name (e.g., ‘2026-05-08-spec-retrieval’). May be a path; the trailing folder name is used.

Example

{
  "tool": "mm_retrieve_prior_work",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "spec_path": "2026-01-15-my-feature"
  }
}

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…