srs-dd / skeleton
CLAUDE.md0 starsChanged 32 days agoMITView on GitHub
AGENTS.md is the shared agent guide for this SRS-DD project, and it is imported here so that every session starts with it in front of you rather than behind a pointer: Claude-specific additions: - Invoke the srs skill before any code change that alters behavior, when planning a task — it also covers multi-requirement plans — and when the question is how the system works rather than a change to it. - To author a new requirement through a dialog,…
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- skeleton/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- srs-arch-auditSkill
- srs-arch-harvestSkill
- srs-archSkill
- srs-auditSkill
- srs-baselineSkill
- srs-betSkill
- srs-buildSkill
- srs-checkSkill
- srs-commitSkill
- srs-harvestSkill
- srs-initSkill
- srs-newSkill
- srs-pageSkill
- srs-releaseSkill
- srs-reviewSkill
- srsSkill
- srs-upgradeSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 9
Invoke the
srsskill: before any code change that alters behavior, when planning a task — it also covers multi-requirement plans — and …
≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<Your Project Name>
AGENTS.md is the shared agent guide for this SRS-DD project, and it is imported here so that every session starts with it in front of you rather than behind a pointer:
@AGENTS.md
Claude-specific additions:
- Invoke the
srsskill before any code change that alters behavior, when planning a task — it also covers multi-requirement plans — and when the question is how the system works rather than a change to it. - To author a new requirement through a dialog, use the
srs-newskill; to audit spec ↔ code drift, test adequacy and the links between requirements, usesrs-audit. - To check a finished change, use the
srs-checkskill — it reads what each touched requirement asks for and offers to run exactly that; to read the specification as a page,srs-page. - To freeze the specification at a milestone, use the
srs-baselineskill — it shows what changed, agrees the number with you, and writes the row; the commit stays yours. - To pick up a new framework version, use the
srs-upgradeskill — one command, no framework clone to keep around.
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.

