Project Health Monitor

As a project grows, it becomes harder to notice things slipping — specs that stall, issues that pile up, tasks that go untouched. Monday Morning’s project health monitor reads your .mm/ folder and produces a structured health report with scores, findings, and specific actions you can take.

What health tracks

The health monitor evaluates your project across several dimensions:

Dimension	What it measures
Spec completion rate	Percentage of specs that have reached “complete” status
Stale specs	Specs with `## In Progress` tasks that haven’t been modified recently
Open issues	Count of unresolved issues, weighted by severity
Blockers	Issues or tasks explicitly tagged as blocking other work
Task velocity	Rate of task completion over recent sessions
Orphaned work	Standalone tasks or issues that aren’t linked to any spec or feature

Each dimension contributes to an overall health score — a simple indicator of whether the project is on track, needs attention, or has problems accumulating.

The /mm:health command

Run a health check from any Claude Code session:

/mm:health

The output includes:

Overall score — a summary rating (Healthy, Needs Attention, At Risk)
Dimension breakdown — individual scores for each area
Findings — specific observations like “3 specs have been in progress for over 2 weeks” or “5 open issues, 2 are critical”
Recommendations — actionable suggestions tied to findings

Example output:

Project Health: Needs Attention (72/100)

Findings:
- 2 specs stale (no activity in 14+ days): auth-flow, payment-integration
- 4 open issues, 1 critical: login-redirect-bug
- 3 standalone tasks with no linked spec

Recommendations:
- Review stale specs: close, archive, or re-prioritize
- Triage critical issue: login-redirect-bug
- Link orphaned tasks to relevant specs or close them

Health scores

The scoring system is intentionally simple:

Score	Rating	Meaning
85-100	Healthy	Work is progressing, few blockers, no stale items
60-84	Needs Attention	Some areas need review — stale specs or accumulating issues
Below 60	At Risk	Significant blockers, many stale items, or critical issues unaddressed

Scores are computed from the raw data in your .mm/ folder. There’s no subjective judgment — the system counts files, checks dates, and applies thresholds.

Acting on findings with /mm:health-fix

When the health report surfaces problems, you can ask Monday Morning to help address them:

/mm:health-fix

This command reads the most recent health findings and offers interactive fixes:

Stale specs — option to archive, re-prioritize, or restart implementation
Orphaned tasks — option to link them to existing specs or convert to issues
Open issues — option to triage, assign priority, or create a spec for complex fixes
Missing implementation files — option to scaffold implementation.md for specs that lack one

Each suggestion is a proposal — you confirm or skip. Nothing is changed without your approval.

When to run health checks

There’s no automatic schedule. Run /mm:health when:

You’re starting a new week and want to assess project state
A sprint or milestone is approaching and you want to check for risks
The project feels “off” and you want a structured diagnostic
You’re onboarding to a project and want a quick assessment

Health checks pair well with AM briefs — run /mm:am for your daily context, and /mm:health for a periodic deeper assessment.

What health doesn’t track

The health monitor reads file state only. It does not:

Measure code quality or test coverage
Track time spent on tasks
Integrate with external project management tools
Judge whether your spec requirements are well-written

It’s a structural health check — are things moving, are things stuck, are things accumulating — not a qualitative review.

Specs & Workflow — the spec lifecycle that health evaluates
Issues & Tracking — how issues feed into health scoring