Individual skill
daily-standup
Produce 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.
plugins/AgiFlow/ai-plugin/skills/daily-standup/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,539
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,701 bytes
Read excerpt
# Agiflow Daily Standup
Give a brief, evidence-based project pulse. Do not modify workspace data.
## Workflow
1. Call `get_current_scope` and resolve the requested project when needed.
2. Call `list_active_tasks_by_org` for current active work.
3. Call `list_work_units` for active and blocked work units.
4. Call `get_project_detail` when the summary is project-specific.
5. Call `list_members` to resolve assignee context.
6. Call `get_task`, `get_work_unit_progress`, or `list_task_comments` only when needed to confirm progress or a blocker.
7. Summarize:
- Done or moved to Review since the latest available update