standuplisted

# /standup Daily standup digest for a Huly project — **project mode is default**. Output is plain text ready to paste into Slack / a standup doc / a meeting summary. **Requires** the `huly` MCP server to be connected. ## Args ``` /standup <PROJECT> [--since 24h|48h|7d] [--by me|EMAIL] ``` - `PROJECT` — identifier or `_id`. **Required.** If missing, call `huly_list_projects` and ask the user to pick (remember within the conversation). - `--since` — lookback window for "yesterday". Default `24h`. Use `72h` after a long weekend. - `--by` — restrict to a single person. `me` resolves via `HULY_EMAIL`. Without `--by`, generate per-assignee blocks for every active member. ## Steps (project mode — default) 1. `huly_list_issues` `{ project, status: "in-progress" }` — today's plate. (For the status filter, first call `huly_list_statuses` `{ project }` and pass the `_id` of the status whose name matches "in progress" / "started" category.) 2. `huly_get_detailed_time_report` `{ project, from: now − since }` — yesterday's effort grouped by `createdBy`. 3. `huly_list_issues` `{ project, limit: 200 }` filtered locally to `status` name in {done, completed} AND `modifiedOn` within window — yesterday's closed issues. 4. For each in-progress issue, `huly_list_issue_relations` `{ identifier }` — collect `is-blocked-by` relations whose target is not in a done/cancelled status. (Tools 1–3 can run in parallel; tool 4 fans out per issue.) ## Steps (--by mode — individual) 1. `huly_get_deta