daily-standup
Skill4 starsChanged 33 days agoMITView on GitHub
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.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- TheVeller/claude-skillstheir own version, first seen Nov 8, 2026
- LindseyB/skillstheir own version, first seen Nov 4, 2026
- fullstackinnoAI/skillstheir own version, first seen Nov 1, 2026
- modimihir07/agentic-ostheir own version, first seen Oct 25, 2026
- leymish01-oss/claude-code-agent-team-startertheir own version, first seen Oct 15, 2026
- ljindong1/claude-skillstheir own version, first seen Oct 15, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- modimihir07/agentic-os★ 209same name
- shahshrey/unclaw★ 17same name
- lglucas/ai-dev-operating-system★ 12same name
- TheVeller/claude-skills★ 4same name
- shalomb/agent-skills★ 3same name
- abdullah1854/ClaudeSuperSkills★ 1same name
- fullstackinnoAI/skills★ 1same name
- LindseyB/skills★ 1same name
- Jinbae10/skills★ 0same name
- leymish01-oss/claude-code-agent-team-starter★ 0same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- backlog-groomingSkill
- getting-startedSkill
- orchestrateSkill
- project-planSkill
- refine-taskSkill
- review-workSkill
- run-taskSkill
- run-workSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 3 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Call get_current_scope and resolve the requested project when needed.
- Very specific: line 13
Call list_active_tasks_by_org for current active work.
- Very specific: line 14
Call list_work_units for active and blocked work units.
- Very specific: line 15
Call get_project_detail when the summary is project-specific.
- Very specific: line 16
Call list_members to resolve assignee context.
- Very specific: line 17
Call get_task, get_work_unit_progress, or list_task_comments only when needed to confirm progress or a blocker.
- Distinctive: line 33
Use short sections titled Done, In Progress, Blocked, and Next Up.
- Distinctive: line 38
Do not claim an item changed recently unless the returned data supports that conclusion.
- Distinctive: line 40
Keep the summary scannable and end with one clear recommendation.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.