leymish01-ossleymish01-oss/claude-code-agent-team-starter/.claude/skills/daily-standup/SKILL.md

daily-standup

Skill0 starsChanged 51 days agoMITView on GitHub

The CEO's daily run. Review the state files, decide today's priorities, update the backlog and journal.

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
ljindong1/claude-skillstheir own version, first seen Oct 15, 2026
thefiredev-cloud/meshvault-harnesstheir own version, first seen Oct 13, 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
AgiFlow/ai-plugin★ 4same 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
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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

0
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read company/STRATEGY.md, company/BACKLOG.md, the top of company/JOURNAL.md, company/DECISIONS.md (latest three entries) and metrics/ if it …
line 8
Very specific:
Update BACKLOG.md: add or re-order tasks so each owner's first READY task is the most valuable one.
line 12
Very specific:
Update STRATEGY.md and DECISIONS.md only if the evidence warrants it.
line 15
Very specific:
Run python3 scripts/check.py and fix anything it reports.
line 19

“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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Act as the ceo agent defined in .claude/agents/ceo.md, following CLAUDE.md.

Read company/STRATEGY.md, company/BACKLOG.md, the top of company/JOURNAL.md, company/DECISIONS.md (latest three entries) and metrics/ if it exists.
Note, for yourself, five lines: the goal, the one metric and its latest real value, the constraint, what changed since the last entry, and what the owner is waiting on.
Update BACKLOG.md: add or re-order tasks so each owner's first READY task is the most valuable one. Keep the table format and the status words exactly as the file defines them. Give every new task the next free ID.
Update STRATEGY.md and DECISIONS.md only if the evidence warrants it. Most days it doesn't.
Prepend a JOURNAL entry under the file's intro text: ## YYYY-MM-DD HH:MM UTC — ceo (get the time with date -u +'%F %H:%M') followed by 2–5 bullets: the constraint, what you changed and why, what's blocked on the owner, and what's next.
Run python3 scripts/check.py and fix anything it reports. Don't run git.

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free