Monday Morning · plan → product

All the ideas.
One executable plan.

Monday Morning condenses your team’s scattered ideas into a ranked, verified plan — briefs, specs, parallel builds, and every claim checked against what actually landed.

↓Downloadfree for two projects

Roadmap · one request, Monday to Friday

roadmap · 3 milestones · ranked

01 · planMON

Write the roadmap once.

Ranked milestones, each a named outcome of three words or less. The roadmap filters everything downstream — it is the plan, not a backlog.

Roadmap · ranked

1Payments live2 specs · 1 queued

2Team accounts2 specs

3Public APIqueued

02 · briefTUE

Describe it in a sentence.

Dispatch drafts a brief — title, intent, provisional tasks — checks it against the roadmap, and files it under its milestone. Off the roadmap? It says so.

rework checkout to support saved cardsDispatch

Brief filed: checkout-refactor

fits roadmap · Payments live · shaped at pickup

03 · shapeWED

Shaped at pickup.

Provisional tasks become final ones, with acceptance criteria a run can be judged against. Nothing vague survives shaping — one spec, one owner.

checkout-refactor · shaping

t1tokenize + store saved cards

t2checkout picks a stored card

t3migration for legacy carts

acceptance · cards persist across sessions

04 · specTHU

Built, claims checked.

The spec runs in its own worktree, parallel where files don’t overlap. Run review verifies every claim on a different model than the builder.

checkout-refactorrunning · wt/checkout-refactor

saved-cards-uirunning · parallel

run review · R1–R6 verified · a checkbox is never proof

05 · productFRI

Shipped, on the record.

Reconcile compares what the run claimed against what landed. Clean work merges; drift goes back. Done means recorded — who, what, and why.

checkout-refactor · done

reconcile clean · claimed 12 · landed 12

1Payments live3/3 · shipped

a changed mind is a new decision, never an edit

SAT · REST

The week ships itself.

Download for macOS →

Principles

Calm, organized, verified.

Agent tooling tends to shout. Monday Morning is built on three quieter beliefs — each one visible in the product.

Calm

Colour signals state, not decoration. Green means running. Ink means it needs a human. Grey is at rest. One accent per view — nothing on the board shouts.

In force — running, verified, an active plan.

Needs a human — an open issue, a question.

Dormant — queued, unshaped, archived.

Organized

The roadmap is a ranked list of outcomes, never a place to author work. Every request becomes a brief, every brief a spec, every spec one owner.

Roadmap · ranked

1Payments live3 specs

2Team accounts2 specs

3Public APIqueued

Verified

A checkbox is execution, never proof. Every run is reviewed on a different model than the builder, and reconcile compares what was claimed against what actually landed on the branch.

Reconcile: checkout-refactorclean

claimed 12 files · landed 12 · checks pass

Teams

The whole team, on one plan.

Claims, running work, and what landed — visible to everyone, without a standup.

Claim a spec so two people never build the same thing. Stolen-claim and staleness signals keep ownership honest.

See the team's running work without asking — active specs, blockers, and what landed, aggregated from everyone's sessions.

Stay local-first. Every spec, task, and decision is plain markdown in your repo — versioned, diff-friendly, no database.

Team · this week4 people · 6 specs

Danacheckout-refactorrunning

Priyasaved-cards-uirunning · parallel

Marcususage-billingneeds review

Samteam-accountsclaimed · 2h ago

this week · 3 specs landed · reconcile clean

The vocabulary

roadmapthe ranked list of milestones — never a place to author workmilestonea named outcome, one line, at most three wordsbriefa spec before shaping — filed by dispatch, shaped at pickupspeca unit of work with final tasks, owned by one persontaskone step inside a spec — a checkbox is execution, never proofagenta session doing a spec’s work — capacity, not a personworktreean isolated checkout per session — why agents never collidedispatchturns a request into a drafted specroadmapthe ranked list of milestones — never a place to author workmilestonea named outcome, one line, at most three wordsbriefa spec before shaping — filed by dispatch, shaped at pickupspeca unit of work with final tasks, owned by one persontaskone step inside a spec — a checkbox is execution, never proofagenta session doing a spec’s work — capacity, not a personworktreean isolated checkout per session — why agents never collidedispatchturns a request into a drafted spec

run reviewverification on a different model than the builderreconcilepost-merge check of what was claimed against what the code showsdecisionan immutable record of resolved judgment — who, what, whyclaimwhat a change asserts it does — tests are evidence, never the claimdefeatera named way a claim could be wrong while checks look greenparallelspecs that run at once because their files don’t overlaprankedordered by dependency, then by what unblocks the mostrun reviewverification on a different model than the builderreconcilepost-merge check of what was claimed against what the code showsdecisionan immutable record of resolved judgment — who, what, whyclaimwhat a change asserts it does — tests are evidence, never the claimdefeatera named way a claim could be wrong while checks look greenparallelspecs that run at once because their files don’t overlaprankedordered by dependency, then by what unblocks the most

In use

“The board tells me what needs me and nothing else. I stopped reading scrollback within a week.”

— Dana · staff engineer, payments

“We plan on Monday and the specs file themselves. Reconcile caught drift our code review had missed twice.”

— Priya · VP engineering, infra

“The quietest tool in my dock, and the one doing the most. It runs the plan; I make the calls.”

— Marcus · founder, devtools

Pricing

Free to start. Pro for the price of two lattes.

One payment, a year of updates, no subscription. Keep what you paid for, forever.

Free

$0forever

The full pipeline for two projectsRoadmap, dispatch, agents, reconcileTwo concurrent sessionsEverything stays in your repo

Download

Common questions

A plan → product pipeline. You write a ranked roadmap; requests become briefs, briefs become specs, agents build them in parallel, and every claim is verified against what actually landed. It runs on your machine as a desktop app.

In your repo. Every spec, task, decision, and note is plain markdown in a .mm/ folder — version-controlled, diff-friendly, portable. No database, no cloud lock-in.

Monday Morning is built tightly around the Claude Code CLI, so dispatch, agents, and reconcile get real, structured access to your project. That focus is what makes the pipeline dependable.

Colour signals state, not decoration — green is running, ink needs a human, grey is at rest. One accent per view, one pulse for live work, and a board that tells you only what needs you.

Free for two projects, forever — the full pipeline included. Pro ($14.99 one-time during beta, $19.99 after) removes the project and session caps; Team ($16/seat/mo) adds shared claims and the team dashboard.

Monday Morning

BETA

Begin Monday with a plan that ships itself.

↓Downloadfree for two projects