Glossary & FAQ
Everything in Monday Morning
Search every feature, integration, agent, skill, and term — plus the questions we hear most.
Frequently asked
- What is an ADE?
- An Agent Development Environment. Where an IDE is built around one person editing one file, an ADE is built around many agents working in parallel — each in its own session, all steered from one place.
- Who is it for?
- Developers who run Claude Code seriously and want to direct several sessions at once instead of babysitting one terminal — across multiple projects, without losing the thread.
- Why Claude Code only?
- Monday Morning is built tightly around the Claude Code CLI and its MCP bridge, so the Conductor gets real, live access to your project. That focus is what makes the fleet workflow work.
- Where does my data live?
- In your repo. Every spec, task, and note is plain markdown in a .mm/ folder — version-controlled, diff-friendly, and fully portable. No database, no cloud lock-in.
- Is my project data sent to the cloud?
- No. Your code and .mm/ data stay local. Semantic-memory embeddings are computed offline inside the MCP server. Integrations are opt-in and talk directly between your machine and the provider.
- What does it cost?
- Monday Morning is free for up to 2 projects, with Pro and Team plans when you need unlimited projects, the full parallel fleet, and team features. See full pricing →
Features21
Reads your whole project, decides quick-fix vs. full spec, dispatches the work, and tells you what to pick up next.
Every Claude Code session live in one responsive grid — add, close, reflow, fullscreen.
Run the fleet in parallel — implement several specs at once, each in its own session and optional git worktree.
Turn a rough idea into a clear plan, broken into steps and tracked to done.
Tasks live in markdown in each spec; the dashboard tracks progress from the files themselves.
Capture architecture decisions, meeting notes, and context as plain markdown.
Track bugs, problems, and blockers alongside your specs and tasks.
Save run, test, and build commands per project and launch them in a click.
Local-first semantic recall — embeddings computed offline in the MCP server, never leaving your machine.
AM/PM briefs rebuild context in seconds — recent changes, in-progress work, blockers, what's next.
Plan the product once; Monday Morning turns the roadmap into features and specs and scaffolds the workspace.
Every spec, task, and note is plain markdown in .mm/ — versioned, diff-friendly, portable.
Preview your web app, docs, API, or build in an embedded webview with native console, network, and device tools.
Run several previews at once in a tab strip, each with its own process and port.
“Fix with Claude” on errors, plus an AI-vision toggle that lets Claude open the page itself via the Playwright integration.
A built-in MCP server gives the Claude Code CLI 60+ tools and live project data — no copy-paste, no context limits.
Ships with 75+ /mm: skills and a roster of agents; browse, import, and toggle skills per project.
Health checks and review reports for your project. (Pro and Team plans.)
Surfaces the most-similar completed specs when you scaffold a new one, so prior patterns carry forward.
Themeable, skinnable UI with design tokens.
Shared check-ins, spec claims, and a team dashboard while every member's code stays local. (Team plan.)
Integrations8
Sync issues and link PRs to specs and tasks.
Post updates and activity digests to channels.
Turn emails into issues, notes, and ideas.
Calendar context for briefs and scheduling. (Coming soon.)
Sync cards and boards with Monday Morning.
Import meeting transcripts and extract action items.
Time tracking, budgets, profitability, and utilization metrics.
Wired into the preview via the AI-vision toggle so Claude can open and inspect your running app.
Agents17
Initializes a spec folder and saves the raw idea.
Gathers detailed requirements through targeted questions and visual analysis.
Writes the detailed specification document for development.
Creates a strategic task list for implementing a spec.
Verifies the spec and its task list before implementation.
Implements a feature by following a spec's task list.
Verifies the end-to-end implementation of a spec.
Runs adversarial checks against a spec to catch gaps.
Creates product documentation — mission and roadmap.
Reviews usability, interaction flow, and design-system consistency.
Designs and refines visual appearance — spacing, color, typography.
Wires up integrations end-to-end across the frontend/backend boundary.
Audits accessibility — keyboard, focus, ARIA, contrast, screen readers.
Diagnoses a bug and traces it to its root cause.
Designs, writes, and hardens tests across the codebase.
Finds and fixes performance bottlenecks.
Audits access control, secret handling, and input validation.
Commands & skills57
Canonical morning brief — recover context for the day.
AM brief (alias for /mm:recap).
End-of-day summary.
Contextual briefing for the current project.
Load project state into the session.
Create a detailed feature spec.
Spec shaping process — gather requirements.
Spec writing process.
Reflection-based spec verification.
Build a strategic task list for a spec.
Start implementing a spec.
Implement all specs.
Implement specs in parallel using git worktrees.
Spec implementation process.
Orchestrate a spec's implementation.
Show spec status.
Order specs for implementation.
Audit and fix spec task status.
Execute a task.
Start a task.
Complete a task.
Full done workflow.
Create a feature grouping.
Capture an idea.
Create an issue.
Close an issue.
Create a project note.
Create a document.
Define product vision.
Plan the product — mission, roadmap, tech stack.
Update the plan for a brownfield project.
Update product context from an existing codebase.
Turn roadmap items into features.
Project health monitor.
Audit-fix-verify health loop.
Code review with optional auto-fix.
Review this project's status.
Review all registered projects.
Run a QA session.
Commit changes.
Generate a changelog.
Generate coding standards.
Codebase analysis Q&A session.
Push a team check-in.
View team check-ins.
Claim a spec from a teammate.
Retrieve similar prior work.
Create a plugin.
Import a skill from a URL or local file.
Improve your Claude Code skills.
Create a proposal.
Create an estimate.
Create a statement of work.
Create a change order.
Set up daily AM/PM routines.
Merge and clean up worktrees.
Set up Supabase authentication.
Concepts7
Where an IDE is built around one person editing one file, an ADE is built around many agents working in parallel — each in its own session, steered from one place.
The open protocol that lets the Claude Code CLI talk to Monday Morning's tools and your connected services.
The git-tracked folder where every spec, task, note, and issue lives as plain markdown and JSON.
The set of Claude Code sessions you run and direct at once across your projects.
A detailed specification for a piece of work, containing tasks — the unit Monday Morning plans and implements against.
A separate git working copy used to implement specs in parallel without conflicts.
Starting each session knowing where you left off — the core problem Monday Morning solves.