Roadmap & Automated Setup

Monday Morning helps you go from a product vision to an executable plan. You start by defining your mission and roadmap, then let Monday Morning turn that roadmap into the features and specs you’ll actually implement. The result is a project that’s scaffolded and ready to build, instead of a blank .mm/ directory.

The planning hierarchy

Planning flows top-down, from broad intent to individual work items:

Level	What it is	Where it lives
Product	Mission, target users, tech stack	`.mm/product/`
Roadmap	Phased list of what you’ll build	`.mm/product/roadmap.md`
Features	Roadmap items that group related specs	`.mm/features/{slug}/feature.json`
Specs	Detailed specifications for a unit of work	`.mm/specs/{date-slug}/`
Tasks	Checklist items inside a spec	`implementation.md`

Each level narrows the scope of the one above it. A roadmap item becomes a feature; a feature gets one or more specs; a spec breaks down into tasks.

Product planning

Planning documents live in .mm/product/:

mission.md — product vision, target users, and core value
roadmap.md — phased development plan
tech-stack.md — technology choices

These files give Monday Morning (and any AI agent working in the project) the context to make decisions that fit your product.

Greenfield: start from scratch

For a new project, run /mm:plan-product (or /mm:plan). Monday Morning walks you through your product idea, target users, key features, and tech stack, then generates all three .mm/product/ files.

Brownfield: backfill from existing code

If you already have a codebase, run /mm:update-plan (or /mm:update-product). Instead of asking you to describe everything from scratch, Monday Morning analyzes the existing project — dependencies, file structure, and any README or manifest files — to detect your tech stack and current features, then asks targeted questions to fill in the gaps. These commands are additive and won’t overwrite existing product docs.

The roadmap

A roadmap is a phased list of work. Phases group related milestones, and each milestone is a checkbox item:

## Phase 2: 1.0 Launch Ready

> Status: in_progress
> Target: 2026-Q3

- [ ] Pro checkout flow and pricing page
- [x] First-launch onboarding
- [ ] Feature gating across all surfaces

Early phases capture foundational work; later phases capture planned and exploratory work. You can keep the roadmap as detailed or as high-level as you like — it’s the source for the automated setup step below.

Roadmap to features: automated setup

Once the roadmap exists, /mm:roadmap-to-features converts roadmap items into Monday Morning features. For each item it creates a folder and a feature.json file:

.mm/features/{feature-slug}/feature.json

A feature is a grouping container — it holds metadata and links to the specs that implement it. This is the automated scaffolding step: instead of hand-creating a folder per roadmap item, Monday Morning generates them for you in one pass.

The command is non-destructive. If a feature with the same slug already exists, it’s skipped rather than overwritten, so you can re-run it after editing the roadmap to sync new items without disturbing existing ones.

From features to specs to tasks

Features are containers; the real work happens in the specs underneath them. For each feature, run /mm:spec {feature-slug} to create a spec linked to it. The spec captures requirements, the detailed specification, and a task breakdown. From there you implement with /mm:spec-start.

The full flow:

Product → Roadmap → Feature → Spec → Tasks → Implement

For everything that happens once a spec exists — the spec lifecycle, the spec folder layout, progress tracking, and wave sequencing — see Specs & Workflow.

Specs & Workflow — the spec lifecycle from planning to verification
The .mm/ Data Model — full reference for the .mm/ directory structure