Skip to content
K

Skills & Agents

Monday Morning ships with a curated library of Claude Code skills — the /mm: command set — and a roster of agents that do the heavy lifting behind those commands. Skills are managed per project: you can browse what’s installed, import new ones from a URL or a local file, and toggle them on or off for the project you’re in. There is no central registry to publish to or pull from; everything lives with your workspace.

Agents come in two flavors. Workflow agents drive the spec pipeline end-to-end. Specialist agents are surfaced as clickable chips in the terminal so you can hand a focused task to the right expert without writing a prompt from scratch.

These agents run the spec lifecycle: shaping requirements, writing the spec, breaking it into a task list, implementing, and verifying. They are invoked by the /mm: skills that orchestrate the pipeline, and several run in their own sessions so stages can proceed in parallel.

AgentWhat it does
spec-initializerScaffolds a new spec folder and its starting files
spec-shaperGathers requirements through targeted questions and visual analysis
spec-writerAuthors the spec from the shaped requirements
spec-verifierReviews the spec for completeness and consistency
tasks-list-creatorBreaks the spec into an implementable task list
implementerImplements the tasks against the codebase
implementation-verifierChecks the implementation against the spec and tasks
adversarial-verifierStress-tests the work, hunting for gaps and regressions
product-plannerDefines product vision and roadmap during planning

The flow is roughly: shape → write → verify spec → task list → implement → verify implementation, with the adversarial pass as an extra layer of scrutiny.

Specialist agents are the mm-* agents surfaced as clickable chips in the terminal. Each is scoped to one discipline, so you can route a review, audit, or fix to the agent best suited for it.

AgentWhat it does
mm-ui-ux-reviewerReviews UI and UX for usability and flow issues
mm-visual-designerHandles visual design and styling work
mm-integrationWires integrations end-to-end across the frontend/backend boundary
mm-a11y-auditorAudits for accessibility issues
mm-debuggerDebugs and traces issues to root cause
mm-qa-engineerPlans and runs QA and testing
mm-perf-optimizerProfiles and optimizes performance
mm-security-auditorAudits for security vulnerabilities

Because specialists run in their own sessions, they compose naturally with the parallel and fleet workflow — you can dispatch several at once and let them work independently while the main spec pipeline continues.

Skill management is per project. From the management UI you can:

  • Browse the skills installed for the current project
  • Import a skill from a URL or a local file
  • Toggle skills on or off so each project only carries what it needs
  • Organize skills per project, with no central registry to sync against

Because configuration is per project, two workspaces can carry entirely different skill sets, and turning a skill off in one project doesn’t affect another.

Several MCP tools back the skill and agent surfaces:

ToolPurpose
mm_create_skillCreate a new skill
mm_import_skillImport a skill from a URL or local file
mm_list_pluginsList installed plugins
mm_get_plugin_infoInspect a specific plugin