Recap & Briefs

Starting a work session is the hardest part. What were you working on? What’s blocked? What should you tackle next? Monday Morning’s briefs answer these questions by reading your project’s current state and producing a focused summary.

The commands

Command	When to use	What it does
/mm:recap	Start of day / returning to a project	The canonical morning brief — a prior-session hand-off, a unified focus list, and your roadmap position
/mm:pm	End of day / stepping away	Reviews today’s work and writes a summary note for the day
/mm:deliberate	Thinking through a specific question	A contextual briefing — loads targeted project context around a stakeholder message, process question, or coordination issue
/mm:schedule-briefs	Once per project	Sets up scheduled routines so recap and PM briefs run automatically each weekday

/mm:am still works — it’s a back-compat alias for /mm:recap, kept so already-scheduled morning routines created against the old name keep running.

The morning brief: /mm:recap

Run this when you sit down to work:

/mm:recap

Under the hood, /mm:recap calls the mm_daily_brief MCP tool (a core tool — agents can call it directly too) and renders its structured JSON. The brief covers:

• Roadmap position — current phase and milestone, with progress percentages
• Active tasks and blockers — what’s in progress across your specs, and what’s stuck, with ages
• Recently completed and upcoming — what just shipped and what’s next in the build order
• Open issues — with severity, so critical items surface first
• Recent commits and PRs — open, unread-comment, and recently merged
• Meetings and Slack inbox — when those integrations are connected

The brief is rendered tersely — one fact per line — and written to disk so the desktop app can surface it. The goal is to get you productive in under a minute instead of opening a dozen files to piece state together.

The end-of-day summary: /mm:pm

Run this when you’re wrapping up:

/mm:pm

The PM brief reads your tasks and issues dashboards, identifies what was completed today, what’s still in progress, and what’s next in the backlog, then writes a summary note for the day. That gives your future self (or a teammate) a clean handoff without a hand-written status update.

Contextual briefings: /mm:deliberate

Not every question is “what should I work on?” Sometimes it’s “how do I respond to this?” /mm:deliberate is deliberation mode: paste a stakeholder message, a process question, or a cross-team coordination issue, and it assembles the targeted project context needed to think it through — the relevant specs, status, and history — rather than a general status dump.

/mm:deliberate "Client asking about merge timeline for the auth work"

Scheduling briefs

/mm:schedule-briefs scaffolds two scheduled routines so /mm:recap runs each weekday morning and /mm:pm runs each weekday evening — without requiring a session to be open at the time. Briefs anchor to the roadmap, so the command checks that .mm/product/roadmap.md exists with phase headers first, and warns you if it doesn’t. The routines persist server-side; run it once per project.

How briefs help with context switching

Modern development often means jumping between projects, repositories, or client work. Each switch has a cost — the time it takes to remember where you left off. Briefs reduce that cost by:

1. Reading project state, not your memory — the brief is generated from files, not from what you remember
2. Surfacing what changed — you see what moved since you last looked, not the entire project
3. Prioritizing next actions — instead of scanning a backlog, you get a ranked list based on current state

If you context-switch between two projects during a day, running /mm:recap on the second project when you return to it is the fastest way to re-orient.

Team alignment

When multiple people work on a project, briefs give everyone the same starting picture. Because a brief is generated from project state — not from anyone’s recollection — two people running /mm:recap see the same factual baseline.

This doesn’t replace standups or communication, but it means everyone starts from the same facts. For the shared team surfaces themselves, see Team Collaboration.

Related

• Specs & Workflow — the spec lifecycle that briefs summarize
• Tasks & Progress — how task status feeds into brief generation
• Review & Health — the periodic deeper assessment that pairs with daily briefs