standup
Generate daily standup summary for current sprint Arguments: <project>.
SKILL.mdplane-ops/skills/standup/SKILL.md
GitHubStandup
Generate a daily standup summary — per-person status, sprint progress, and blockers.
Arguments
Format: <project>
- project: Project name or identifier (required)
Parse from "$ARGUMENTS".
Process
Bootstrap connector — consult the
connector-bootstrapskill. ProbeToolSearchfor the Plane resource tools referenced below (project,member,cycle,workitem,workitem_relation); their names aremcp__<server>__<resource>, never assume a specific MCP prefix. If multiple Plane instances are connected, ask the user which one to use. All formulas and rules come from theagile-fundamentalsskill. Calls are writtenresource(action=..., ...).Find active sprint:
cycle(action=list, project_id, status=current)The cycle where today is between start_date and end_date.
Get sprint items and team:
cycle(action=list_workitems, project_id, cycle_id) member(action=list_project, project_id) workitem(action=count, project_id, pql='cycle = "<cycle_id>"', group_by=state__group)The count gives the state-group totals in one call.
Group items by assignee and state: For each team member:
- Completed: items in "completed" state group
- In Progress: items in "started" state group
- Not Started: items in "unstarted" state group
Detect blockers: For in-progress items, check:
workitem_relation(action=list, project_id, workitem_id) cycle(action=list_workitems, project_id, cycle_id, pql='stateGroup = "started" AND updatedAt < daysAgo(2)')Flag items with "blocked_by" relations, and items in progress that have not changed for 2+ days (stalled candidates).
Calculate sprint progress:
- Total/completed/remaining points
- Days elapsed and remaining
- Pace vs needed pace
- WIP count vs limit
Display standup report: Per-person summary (done, doing, blocked) + team-level sprint progress.
Example Usage
/standup "TaskFlow"
/standup "My Project"