mm_complete_task

Mark a task done with cascading rollups. Runs project tests first — fails if tests fail (unless force: true). Checks if all spec tasks are complete, then if all feature specs are complete, and updates statuses accordingly.

At a Glance

• Category: Workflows
• Source: Built-in
• Required parameters: 3
• Total parameters: 5

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root
spec_path	string	Yes	Spec folder name (e.g., ‘2025-12-09-badges’)
task_title	string	Yes	Title of the task to complete
force	boolean	No	Bypass the test gate. Use for non-code tasks, flaky tests, or when tests already passed in a prior step.
skip_verify	boolean	No	Skip auto-verification when spec completes. Use when you want to batch-verify later.

Example

{
  "tool": "mm_complete_task",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "spec_path": "2026-01-15-my-feature",
    "task_title": "My Example",
    "force": true,
    "skip_verify": true
  }
}

Related Tools

• mm_plan_feature - Create a complete feature scaffold in one call — creates the feature, creates…
• mm_daily_brief - Generate a structured morning summary with active tasks, blockers, recently c…
• mm_suggest_next - Recommend what to work on next based on in-progress tasks, feature priority, …
• mm_get_guidance - Get contextual guidance suggestions based on project state
• mm_start_task - Mark a task as in-progress and return context for starting work — spec conten…