Show the gh-pms dashboard for the current repo — open issues grouped by status, WIP for current user, next-actionable items. Auto-invoke when the user says "status", "where are we", "what's next", "show issues".

Project-management dashboard for the current repo.

What it does

Determine repo from git remote get-url origin
Detect features via ${CLAUDE_PLUGIN_ROOT}/lib/ghcall.sh detect-features
If a gh-pms Projects v2 board exists, prefer reading it (single canonical view of Status, Severity, Effort, Service across the whole project):
bash
Group by Project's Status field. Within each Status bucket, sort by Severity (Critical → High → Medium → Low) so the most urgent items surface first regardless of kind. Severity values come from workflows/default.yaml.severities.values[].
Otherwise (no project), fall back to label-based grouping:
- mcp__github__list_issues — all open issues, grouped by status:* label
- Within each group, sort by severity:* label using the same Critical → Low order
- Issues assigned to current user with status:in-progress
- Open type:request issues
Always include milestone progress via gh api repos/{owner}/{repo}/milestones?state=open — show plans (= milestones) with their progress bars
Render a grouped table:

text

Notes

"Started Xh ago" comes from the local state file
"N/M sub-issues done" comes from counting closed children of the plan via mcp__github__list_issues filtered by parent
"Blocked by #X" reads from issue body's **Depends on**: #X line
Velocity is computed by summing the effort:* labels (or Project v2 Effort field) of issues closed in the last 7 days. S/M/L/XL count as 1/3/5/8 story-points equivalent for the throughput line. Issues without an effort don't contribute (so unestimated work doesn't skew the metric)