pm-status-reportlisted

# /pm-status-report Stakeholder-grade comprehensive status report for a Huly tracker project. ~10 sections including an exhaustive component-grouped task list. **Read-only**, no writes to Huly. **Requires** the `huly` MCP server. ## Args ``` /pm-status-report <PROJECT> [--period 7d|30d|sprint] ``` - `PROJECT` — identifier or `_id`. **Required.** - `--period` — reporting window: - `7d` (default) — last 7 days - `30d` — last 30 days - `sprint` — auto-detect the active milestone (`status == 1`); use its start (`createdOn` of milestone) → `target_date` as the window ## Tools called Run in two waves. Wave 1 (parallel) gathers the dataset; wave 2 fans out for relations / supplementary sets. **Wave 1:** 1. `huly_get_project` `{ project }` — name, identifier, archived flag. 2. `huly_list_statuses` `{ project }` — `_id` → name + category map; defines the **status column order** for the breakdown. 3. `huly_list_components` `{ project }` — `_id` → label map. 4. `huly_list_issues` `{ project, limit: 500 }` — main dataset. 5. `huly_list_milestones` `{ project }` — full milestone state. 6. `huly_get_detailed_time_report` `{ project, from: <period start> }` — effort in period, grouped by issue + assignee. 7. `huly_list_time_spend_reports` `{ project, from: now − 8 weeks }` — velocity trend. 8. `huly_list_documents` (only if a teamspace is known — typically skipped unless the user provided one) for doc coverage. 9. `huly_list_test_runs` — only if a QMS test project shares the p