mm_create
Create a Monday Morning entity. The entity discriminator chooses the per-type handler. Replaces the deprecated mm_create_*, mm_add_task, and mm_notify tools.
At a Glance
Section titled “At a Glance”- Category: Core
- Source: Built-in
- Availability: Listed by default
- Required parameters: 1
- Total parameters: 35
Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
entity | string (enum: spec, feature, issue, doc, skill, from_email, task, notification, quick, note, idea) | Yes | Entity type to create. |
project_path | string | No | All entities: absolute path to the project root (the directory containing .mm/). |
name | string | No | entity=spec: spec name (e.g., ‘Prompt System’). entity=feature: display name for the feature. entity=skill: display name for the skill. |
feature_id | string | No | entity=spec only: feature ID to link this spec to (optional). |
description | string | No | entity=spec: description for spec.md. entity=feature: feature description. entity=issue: issue description (required). entity=skill: detailed description of when/how to use this skill (used for discovery). |
depends_on | array of string | No | entity=spec only: spec folder slugs (YYYY-MM-DD-slug) that must complete before this spec — written into spec.md depends_on: frontmatter to drive build-order waves. |
idea_folder | string | No | entity=spec only: path to the source idea folder (e.g. ‘.mm/ideas/2026-05-18-my-idea’ or an absolute path). When provided, shaped_to: <new-spec-folder> is appended to the idea’s frontmatter. |
issue_path | string | No | entity=spec only: path to the source issue file (e.g. ‘.mm/issues/2026-06-04-bug-title.md’ or an absolute path). When provided, converted_to: ./specs/<new-spec-folder> is written into the issue’s frontmatter. |
skip_prior_work | boolean | No | entity=spec only: skip auto-generation of prior-work.md. Used by tests; production callers should leave this false. |
skip_feature_match | boolean | No | entity=spec only: skip auto-matching / auto-creating a feature when feature_id is omitted. Used by tests that need an unlinked spec. |
auto_feature | boolean | No | entity=spec only: opt in to auto-match an existing feature (or auto-create a new one) when feature_id is omitted. Default false — specs are created UNLINKED. |
source_plan | string | No | entity=spec only: plan slug this spec was promoted from (e.g. ‘orchestration’ for .mm/plans/orchestration.md). |
source | string | No | entity=spec only: the roadmap item, instruction, conversation, or issue that prompted this spec — written into spec.md source: frontmatter for intent tracing. |
id | string | No | entity=feature: feature slug (auto-generated from name if omitted). entity=skill: skill ID/slug (auto-generated from name if omitted). |
priority | string | No | entity=feature: priority level (high|medium|low). entity=quick: priority (default: medium; high|medium|low). |
title | string | No | entity=issue: issue title. entity=doc: doc title. entity=quick: quick task title. entity=task: task title (single-task mode; use titles for a batch). entity=notification: notification title. entity=note: note title. entity=idea: idea title. |
severity | string | No | entity=issue: issue severity (default: medium). entity=notification: severity level (default: info; info|warning|error). |
category | string | No | entity=doc: doc category (e.g., ‘api’, ‘architecture’, ‘onboarding’, ‘runbook’; default ‘general’). entity=note: note category (Decision, Meeting, Research, Architecture, Development, Other; default Development). |
source_url | string | No | entity=doc only: external URL where the canonical doc lives (GitHub wiki, Notion, etc.). |
content | string | No | entity=doc: initial markdown content for the doc file. entity=note: note body markdown (everything below the title/category header). |
raw_idea | string | No | entity=idea only: the idea as captured — keep it in the user’s words. |
problem | string | No | entity=idea only: what problem it solves / why it matters (omit → ‘To be explored during shaping’). |
approaches | string | No | entity=idea only: initial implementation thoughts (omit → ‘To be explored during shaping’). |
open_questions | array of string | No | entity=idea only: extra open questions beyond the standard MVP-scope/priority pair. |
linked_spec | string | No | entity=doc: spec folder name to auto-link this doc to (adds a → spec: reference). entity=quick: optional linked spec folder name. |
use_cases | array of string | No | entity=skill only: list of when-to-use bullet points. |
guidelines | array of string | No | entity=skill only: list of guidelines or rules for this skill. |
message_id | string | No | entity=from_email only: Gmail message ID to import. |
thread_id | string | No | entity=from_email only: Gmail thread ID to import (imports all messages). |
entity_type | string (enum: issue, note, idea) | No | entity=from_email only: target entity type to create from the email. |
spec_path | string | No | entity=task only: path to spec folder (e.g., ‘.mm/specs/2025-12-09-badges’ or just ‘2025-12-09-badges’). spec_folder is also accepted as an alias. |
titles | array of string | No | entity=task only: batch mode — create all listed tasks in ONE call (single read-modify-write of the spec). Prefer this over N sequential single-title calls. |
subtasks | array of string | No | entity=task only: optional list of subtask titles (single-task mode only). |
status | string | No | entity=task: task status (default: backlog), applied to every created task. entity=quick: initial status (default: building). |
body | string | No | entity=notification only: notification body text. |
Example
Section titled “Example”{ "tool": "mm_create", "arguments": { "entity": "spec", "project_path": "/Users/you/projects/my-app", "name": "My Example" }}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…