pm-riskslisted

# /pm-risks Risk radar for a Huly tracker project. Surfaces issues / milestones that need PM attention this week. **Output only — never writes to Huly.** **Requires** the `huly` MCP server. ## Args ``` /pm-risks <PROJECT> [--stale-days 7] [--block-threshold 3] ``` - `PROJECT` — identifier or `_id`. **Required.** If missing, ask. - `--stale-days` — threshold for "stuck" rule. Default `7`. - `--block-threshold` — minimum dependents for the "bottleneck" rule. Default `3`. ## Steps 1. `huly_list_statuses` `{ project }` — map status `_id` → name + category, identify which statuses are `done` / `cancelled`. 2. `huly_list_issues` `{ project, limit: 500 }` — full dataset. 3. `huly_list_milestones` `{ project }` — milestone status + target dates. 4. `huly_get_detailed_time_report` `{ project }` — used for over-budget rule. 5. For top in-progress / high-priority issues, call `huly_list_issue_relations` `{ identifier }` to count how many issues each one blocks. (Only fan out for the top ~30 candidates to keep latency reasonable.) ## Risk rules Apply each rule against the dataset. Each rule produces zero or more risk records with `{severity, rule, identifier|milestone, title, details}`. | Severity | Rule | Condition | |---|---|---| | 🔴 HIGH | Overdue | `dueDate < now` AND status not in done/cancelled | | 🔴 HIGH | Milestone at risk | Milestone `status == 1 (in-progress)` AND `target_date < now + 7d` AND `> 30%` of its issues still open | | 🔴 HIGH | Critical bottleneck | Issue