project-status
Skill6 starsChanged 7 days agoMITView on GitHub
Summarizes the current state of the project (version, branch flow, work in progress, epics, PRs, debt, recent decisions, pending migrations) and answers what can be started now, generated on the spot from git, GitHub and the docs. Use with "/project-status", "what state is the project in?", "catch me up", "what can I do now?", "what's next?", "what is blocked?" or when starting a new session.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- odytrice/metaskillstheir own version, first seen Nov 15, 2026
- eranw2000/claude-maintenance-skillstheir own version, first seen Nov 8, 2026
- desertcache/agent-ostheir own version, first seen Nov 1, 2026
- MrEddieO/claude-skillstheir own version, first seen Oct 20, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- eranw2000/claude-maintenance-skills★ 8same name
- ozgurkarahan/ai-agent-memory★ 8same name
- AJBcoding/claude-skill-eval★ 4same name
- korchasa/flowai★ 3same name
- Manshooo/astral-genesis★ 3same name
- fullstackhouse/skills★ 1same name
- odytrice/metaskills★ 1same name
- philpalmieri/engineering-manager-skills★ 1same name
- Tracebrain/mcp★ 1same name
- desertcache/agent-os★ 0same name
5 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- llms.txtllms.txt
- add-memberSkill
- create-issueSkill
- db-migrationSkill
- debugSkill
- git-workflowSkill
- implement-issueSkill
- improve-skillsSkill
- orchestrateSkill
- plan-featureSkill
- remove-memberSkill
- review-prSkill
- update-docsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If something looks odd (an old open PR, an unassigned critical issue, a release open for weeks), mention it in one line.
- Distinctive: line 30
If the user says which area or priority they want to work on, filter the list with that.
- Very specific: line 31
If there are available ones with status:triage, mention it: they have no priority yet.
“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
Project status
.claude/skills/project-status/status.shIt generates the summary on the spot from the sources (git, issues, PRs, ADRs, docs/agents-map.json). It is deliberately not saved to a file: a committed summary ages as soon as nobody regenerates it and ends up saying something false with an official look.
When answering:
- Show the output and, if the user wants more, go deeper with the sources it cites (
architecture.md, the epic, the ADR). - If something looks odd (an old open PR, an unassigned critical issue, a release open for weeks), mention it in one line.
What can be done now
For "what can I do now?", "what's next?", "what is blocked?":
.claude/skills/project-status/available.shIt returns four lists: can be started now (no open blockers and unassigned, by priority), in progress (assigned or with an open PR that closes them, with who and which PR), blocked (with what blocks them) and epics in progress (with sub-issue progress). Epics do not show up as available: they are worked through their sub-issues. Taken ones do not either: /implement-issue assigns the issue when it takes it, and an open PR that closes it (through Closes #n in the body or the number in the branch) counts too. That way two sessions do not pick the same one.
When answering:
- Show the output as is, without inventing issues that are not there.
- If the user says which area or priority they want to work on, filter the list with that.
- If there are available ones with
status:triage, mention it: they have no priority yet. - GitHub takes a few seconds to update the dependency summary: if an issue was just closed, it may still show for a few more seconds.
It changes nothing, so no confirmation is needed.
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.

