메뉴
Read-only project pulse: what got done, what's in progress, what's blocked, and what's next. Use for daily orientation or stakeholder summaries. Invoked as /agiflow:daily-standup. Uses list_tasks, list_active_tasks_by_org, list_work_units, get_work_unit_progress.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | daily-standup |
| description | Read-only project pulse: what got done, what's in progress, what's blocked, and what's next. Use for daily orientation or stakeholder summaries. Invoked as /agiflow:daily-standup. Uses list_tasks, list_active_tasks_by_org, list_work_units, get_work_unit_progress. |
| tags | ["agiflow","mcp","standup","reporting"] |
| metadata | {"mirrors":"backend/apis/agiflow-api .../prompts/dailyStandup.md"} |
Invoked as
/agiflow:daily-standup. In hosts without slash-prompts, this skill is triggered by matching intent and drives AgiFlow via its MCP tools.
Usage:
/agiflow:daily-standup - Get today's standup summary/agiflow:daily-standup <project-slug-or-id> - Standup for a specific projectExamples:
/agiflow:daily-standup (org-wide standup)/agiflow:daily-standup my-project (project-specific standup)Purpose Provide a quick daily pulse: what happened, what's next, what's blocked. Designed for the start-of-day check-in — users open the app and want a 2-minute overview, not a deep dive.
Guardrails
Follow the shared AgiFlow project-management guidelines in references/agiflow-agents.md — agent assignment, the task status workflow and transitions, work-unit best practices, and the tags strategy apply to this workflow.
Steps
list_active_tasks_by_org MCP tool to get all active tasks.list_work_units MCP tool with status: "in_progress" to get active work units.get_project_detail for focused view.list_members MCP tool to understand who's working.Identify recently completed work:
Summarize completions:
Identify current active work:
For each active item:
Identify blockers:
For each blocker:
Priority logic:
## Daily Standup
### Done (since last check)
- [task slug] [title] — completed by [assignee]
- [task slug] [title] — moved to review
### In Progress
- [task slug] [title] — [assignee], [N/M] acceptance criteria done
- [WU slug] [title] — [N/M] tasks complete
### Blocked
- [task slug] [title] — [blocker description]
### Next Up
1. [Recommended action] — [why]
2. [Second recommendation] — [why]
### Quick Stats
- Active tasks: [N] | Completed today: [N] | Blocked: [N]
If nothing happened since last check, say so clearly: "No changes since last standup. Current focus: [what's in progress]."
Common Mistakes to Avoid
Groom Planning tasks: verify readiness, prioritize, promote to Todo, and group into 3-8 task work units. The only gate from Planning to Todo. Invoked as /agiflow:backlog-grooming. Uses list_tasks, update_task, reorder_tasks, batch_create_work_units, list_work_units.
Coach the user through AgiFlow project management and route them to the right workflow (plan/groom/execute/review). Use when the user is new to AgiFlow, asks 'where do I start', or wants a workflow overview. Invoked as /agiflow:getting-started; also triggers on AgiFlow onboarding intent. Uses get_project_detail, list_work_units, list_tasks, list_members.
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses list_tasks, list_active_tasks_by_org, list_members, update_task, get_work_unit_progress.
Plan a project or feature: research context, clarify requirements, decompose into vertical slices, and create tasks in Planning status. Use when starting new work or breaking down requirements. Invoked as /agiflow:project-plan <requirements>. Uses get_project_detail, list_tasks, list_work_units, create_task, batch_create_tasks.
Refine a task into a complete, autonomous-ready spec with SMART acceptance criteria, technical context, and AI-readiness checks. Use when a task is vague or keeps getting rejected. Invoked as /agiflow:refine-task <task>. Uses get_task, update_task, list_tasks, create_task_comment, list_artifacts.
Quality gate: verify each acceptance criterion of a completed task/work unit, run quality checks, and create follow-up tasks for gaps. Use before merging or to audit delivered work. Invoked as /agiflow:review-work <work-unit-or-task>. Uses get_work_unit, get_task, update_task, create_task, create_task_comment.