// Surface blockers, overdue tasks, and stale items across active projects. Queries the pm_essentials_* tables via the plugin's readonly-data endpoint. Use when the user asks 'how are projects doing?', 'what's blocked?', or wants a health check before a leadership review.
Generate a ≤ 150-word stakeholder status update from plugin data — Accomplishments | In Progress | Blockers | Next Steps. Use when the user asks for a weekly status, leadership update, or sprint recap.
Plan a sprint from the PM Essentials plugin — break down a sprint goal into 5-10 tasks, estimate effort (XS/S/M/L/XL), assign owners, and output a Markdown table. Use when the user says 'plan a sprint', 'sprint planning', or provides a sprint goal and wants it decomposed into tasks.
| name | project-health |
| description | Surface blockers, overdue tasks, and stale items across active projects. Queries the pm_essentials_* tables via the plugin's readonly-data endpoint. Use when the user asks 'how are projects doing?', 'what's blocked?', or wants a health check before a leadership review. |
| argument-hint | [optional project name to narrow the scope] |
Produce a compact health snapshot of active projects.
GET /api/plugins/pm-essentials/readonly-data/open_projects — active projects with task counts and due datesGET /api/plugins/pm-essentials/readonly-data/sprint_tasks — tasks in the active sprint### Project health — <YYYY-MM-DD>
**<Project name>** — <N tasks>, due <date>
- ✓ <count_done> done · ⟳ <count_in_progress> in progress · ◯ <count_todo> todo
- 🚩 <blocker_summary or "no blockers">
**<Next project>** …
open_projects and sprint_tasks.$ARGUMENTS names a project, filter to that one (case-insensitive contains match).in_progress for more than 7 days → "stuck"due_date with status ≠ done → "overdue"started_at + 14 days with tasks still in todo → "slipping"open_projects → reply "No active projects. Create one via the chat with pm-nova."sprint_tasks empty but projects exist → note "no active sprint" under each project.