executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
daily-standupProduce a concise read-only Agiflow status summary covering completed work, work in progress, blockers, and recommended next priorities. Use for daily standups, morning checks, stakeholder updates, or a quick project pulse.
Independent GitHub snapshot · Automated classification · Original documentation governs
Give a brief, evidence-based project pulse. Do not modify workspace data.
get_current_scope and resolve the requested project when needed.list_active_tasks_by_org for current active work.list_work_units for active and blocked work units.get_project_detail when the summary is project-specific.list_members to resolve assignee context.get_task, get_work_unit_progress, or list_task_comments only when needed to confirm progress or a blocker.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.