standup
Skill1 starsChanged 2 months agoMITView on GitHub
Reconstruct project status and next actions from checkpoints, Git, and durable project instructions within an explicitly chosen scope.
55 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- HsuanYuLee/polaristheir own version, first seen Nov 5, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
- AuroraBackcountry/agent-configtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use close-day, meeting-prep and 10 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 versions55 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 55
- anthropics/knowledge-work-plugins★ 35ksame 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
- jcurbelo/agent-seed★ 8same name
- zauberzeug/game-of-cards★ 7same name
45 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 repository39 other files it gives its agents.
- apple-native-motionSkill
- apple-ui-copySkill
- audit-macos-appSkill
- brain-wikiSkill
- catch-me-upSkill
- checkpointSkill
- claude-md-coachSkill
- claudeSkill
- codexSkill
- crash-debuggingSkill
- cut-memorySkill
- explaining-problemsSkill
- file-batch-safetySkill
- handoffSkill
- heads-downSkill
- hopper-mcpSkill
- icon-designSkill
- interface-integritySkill
- ios-defaultsSkill
- kitSkill
- macos-defaultsSkill
- mock-and-pickSkill
- obsess-heroSkill
- obsessSkill
- offline-archiveSkill
- os-workaroundsSkill
- paper-mcpSkill
- predictionSkill
- second-loopSkill
- session-auditSkill
- ship-macosSkill
- show-meSkill
- slice-and-reviewSkill
- slow-modeSkill
- spatial-interfacesSkill
- synthetic-fixturesSkill
- transitional-interfacesSkill
- web-design-defaultsSkill
- window-captureSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Generic directory: ask which project root or configured project registry to use.
- Distinctive: line 16
If discovery produces an unexpectedly large set, show the count and roots before a deep read.
- Distinctive: line 26
Do not fix, clean, commit, or invent a next step during gathering.
“Common” is measured: kept by at least 6 in 10 of the 51 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
Use this skill only when invoked. The user cannot hold every project's live state in working memory; this reconstructs it from durable evidence in one message. The working directory supplies the first scope candidate—scope is part of the answer, not a reason to silently omit quiet work.
Choose scope
- Project root: report that project in depth.
- Container with several projects: inventory one level down, report the count, and cover every discovered project unless the user narrows it. No recency cutoff and no count cap.
- Generic directory: ask which project root or configured project registry to use. Do not guess personal development roots.
If discovery produces an unexpectedly large set, show the count and roots before a deep read. Recency orders the report; it does not silently exclude quiet projects.
Gather read-only evidence
For each project:
- Relevant unarchived
.checkpoints/files and a legacyCHECKPOINT.md, if present. - Current branch, last meaningful commit and date, ahead/behind state, and
git status --porcelain. - AGENTS.md, CLAUDE.md, or the opening of README when nothing else explains the project.
Do not fix, clean, commit, or invent a next step during gathering.
Report
For a container, give one entry per project: name, last activity, plain-language state, recorded next step, and a visible dirty-worktree marker. For one project, include current phase, recent changes, live plates, contradictions between checkpoint and repository, and the best-supported next action.
Payload first. Quiet is a real state, not noise. “No recorded next step” is valid; do not invent momentum to make the report feel complete. Recommend the hottest supported thread when one is obvious, then ask which thread to resume.
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.