standup
Skill8 starsChanged 8 months agoMITView on GitHub
Morning standup - scan todos from yesterday, plan today. Run every morning to start the day.
56 other projects use a version of this.
Adopted by
Most recently taken up by
- saksham10arora-dotcom/everything-claude-codextheir own version, first seen Nov 15, 2026
- HsuanYuLee/polaristheir own version, first seen Nov 12, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- spencerldixon/skillstheir own version, first seen Nov 8, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
Used with
Projects with it also use close-day, meeting-prep and 9 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
vantageos-agencySkillclose-day
End-of-day routine: close tasks with their time, leave the repository and the disk clean, write the diary, harvest friction, and hand over to tomorrow. Use this skill whenever the user says "close day", "end of day", "fin de journée", "bonne nuit", "wrap up", "call it a day", "close session", "daily close", or mentions ending their work session -- even if they don't say "close-day" explicitly.
Also in 3 projects that use this
OpenAISkillmeeting-prep
Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.
Also in 5 projects that use this
jasonmichaelbell78-creatorSkilltodo
Cross-session todo management with interactive menu, JSONL-backed persistence, and AI-powered context capture. Manages ideas, tasks, and insights that emerge during sessions so they survive across sessions. Independent of GSD.
Also in 3 projects that use this
takleb3rrySkillkickoff
Initialize a new project by analyzing source documents and generating requirements.md and design.md
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 4 projects that use this
GitHubSkillrefactor
Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
Also in 4 projects that use this
Other versions56 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 56
- anthropics/knowledge-work-plugins★ 36ksame name
- saksham10arora-dotcom/everything-claude-codex★ 96same name
- drafthq/draft★ 40same name
- shipshitdev/skills★ 39same name
- rlajous/claude-code-commands★ 30same name
- GTMify/aigtm★ 25same name
- kriscard/Skills★ 15same name
- carlvellotti/codex-for-pms-skills-bonus★ 8same name
- edjchapman/claude-code-config★ 8same name
- zauberzeug/game-of-cards★ 7same name
46 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.
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Before anything else, pull the latest from main:
- Very specific: line 19
Memory Check: Read memory/MEMORY.md for any pending items or context from previous sessions.
- Very specific: line 21
If integration agents are available (check .claude/agents/index.md), also scan:
- Distinctive: line 26
Run available scans in parallel using the Task tool.
- Distinctive: line 32
If something was already handled, mark it done — don't roll it over
- Very specific: line 37
Create today's folder at todos/YYYY-MM-DD/ with todos.md, drafts/, notes/
- Distinctive: line 39
Add new items from scans
- Distinctive: line 45
After creating the todo file:
“Common” is measured: kept by at least 6 in 10 of the 52 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
/standup - Morning Standup
Step 0: Pull Latest
Before anything else, pull the latest from main:
git pull origin mainThis ensures todos, memory, and skills are up to date.
Step 1: Scan
- Yesterday's Todos (use todo-manager agent): Read the most recent
todos/YYYY-MM-DD/todos.md. Identify incomplete items to roll over. Use today's date to calculate yesterday. - Memory Check: Read
memory/MEMORY.mdfor any pending items or context from previous sessions.
If integration agents are available (check .claude/agents/index.md), also scan:
3. GitHub (if pr-agent or github agent exists): Check for PRs pending review, overnight merges.
4. Issue Tracker (if tracker agent exists): Pull recently updated issues.
5. Messages (if slack-reader agent exists): Check for mentions and DMs.
Run available scans in parallel using the Task tool.
Step 2: Reconcile
Before creating todos:
- Cross-reference yesterday's incomplete items against any overnight activity
- If something was already handled, mark it done — don't roll it over
- Deduplicate items that appear in multiple sources
Step 3: Create Today's Todos
- Create today's folder at
todos/YYYY-MM-DD/withtodos.md,drafts/,notes/ - Roll over genuinely incomplete items
- Add new items from scans
- Prioritize: High / Medium / Low
- Give a concise briefing: what's urgent, what's in progress, what can wait
Step 4: Commit and PR
After creating the todo file:
- Create branch:
chore/standup-YYYY-MM-DD - Stage the new
todos/YYYY-MM-DD/folder - Commit:
chore: standup YYYY-MM-DD - Push and create PR (if
ghis available), otherwise commit to current branch
End by asking: "Anything else you want to add to today's list?"
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.

