Agiflow Daily Standup
Give a brief, evidence-based project pulse. Do not modify workspace data.
Workflow
- Call
get_current_scopeand resolve the requested project when needed. - Call
list_active_tasks_by_orgfor current active work. - Call
list_work_unitsfor active and blocked work units. - Call
get_project_detailwhen the summary is project-specific. - Call
list_membersto resolve assignee context. - Call
get_task,get_work_unit_progress, orlist_task_commentsonly when needed to confirm progress or a blocker. - Summarize:
- Done or moved to Review since the latest available update
- Current work in progress
- Blocked or stalled items
- Highest-priority next actions
Priority Logic
- Resolve blockers that prevent other work.
- Finish existing work in progress before starting more work.
- Select the highest-priority ready item.
- Recommend refinement when a task is not ready.
Output Format
Use short sections titled Done, In Progress, Blocked, and Next Up. Include task or work-unit identifiers when available. State clearly when no recent changes or blockers are found.
Guardrails
- Remain read-only. Do not call mutation tools.
- Do not claim an item changed recently unless the returned data supports that conclusion.
- Distinguish confirmed blockers from possible signs of stalled work.
- Keep the summary scannable and end with one clear recommendation.
Source: hashgraph-online/awesome-codex-plugins → plugins/AgiFlow/ai-plugin/skills/daily-standup/SKILL.md