srs
Skill0 starsChanged 32 days agoMITView on GitHub
Working with the project specification (SRS in specs/). Invoke ALWAYS before any code change that alters behavior; when planning any task — including planning a feature, breaking a task into steps, or sequencing work across several requirements; when asked what the system should do; when investigating why something is built the way it is; when changing or cancelling a requirement. For a guided dialog that authors a brand-new requirement, prefer the srs-new skill. Not needed only for changes that do not touch behavior — typos, formatting, comments.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- gr219/OpenBA-Kittheir own version, first seen Oct 25, 2026
- spmtitsolution/OpenBA-Kittheir own version, first seen Oct 20, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- spmtitsolution/OpenBA-Kit★ 38same name
- gr219/OpenBA-Kit★ 0same name
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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- skeleton/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- skeleton/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
- srs-upgradeSkill
The file
We split this skill 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 15
Read what the project says of itself: specs/00-glossary.md, specs/01-introduction.md, specs/02-overview.md — short, and in its own words.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill 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
<!-- Copyright (c) 2026 CRELLIA S.L. — part of SRS-DD, distributed under the MIT License -->Working with the specification
The rules of the format are in srs-dd/standard.md, by section, and are not restated here.
python3 srs-dd/tools/srs_view.py --vocabulary prints the words a block may use — statuses, fields, areas, modal verbs; open the standard for a rule, not for a word.
Statements, titles and rationales are written in the lexicon of specs/srs-config.json, whatever language this file is in.
A question about the system
- Read what the project says of itself:
specs/00-glossary.md,specs/01-introduction.md,specs/02-overview.md— short, and in its own words. A lookup by number needs a number nobody has handed you; a search finds the word you guessed. - Narrow:
python3 srs-dd/tools/srs_view.py --areas, thenpython3 srs-dd/tools/srs_view.py --list --area <AREA>, thenpython3 srs-dd/tools/srs_view.py <ID>, then--code <path>. - Where the specification does not say, name the rungs you walked — the area, the words, the paths. Where the question is undecided,
specs/91-open-issues.mdholds it; read an entry whole.
Before changing code
python3 srs-dd/tools/srs_view.py --code <path> --statements— the requirements behind the file, from thecodeandtestsfields and, for a file, its own annotations, each with what it obliges; a directory works. Without the tool:grep -rn "<path>" specs/and the table inspecs/90-traceability.md, whose Incoming links section is every link in one place.- Read what the answer names:
python3 srs-dd/tools/srs_view.py <ID> --whereprints every annotated line that carries the requirement, andpython3 srs-dd/tools/srs_view.py <ID> --where --sourceprints the region each marks; where its header says nosrs-end:ended it, read on in the file. Read those, in one call, before any file whole. A file the fields name that no line speaks for is printed as such, and is the one to open. A search over the repository is the fallback, taken out loud (AGENTS.md). - Found some: choose by the statements the ones the change will touch, and read those in full —
python3 srs-dd/tools/srs_view.py <ID>resolves the links both ways — with what eachderives_fromanddepends_on. Incoming links are the blast radius; the rest of the list is known by its statements and is not opened. - Found nothing: the behaviour is undescribed. Author a requirement first (
srs-new); never code silently. - With a
grounds/directory besidespecs/:python3 srs-dd/tools/srs_grounds.py --blast <path>— what the requirements stand on.refutedorexpiredis not a stop; it is said, because the change inherits that ground. Procedure:srs-bet. - With an
arch/directory:grep -n <path> arch/90-map.md, or the directory above it, since a directory incarriesowns what is under it — the row names the element the file belongs to, what else it carries and the requirements it holds. A change that moves a responsibility between parts is said, not left for the checker. Procedure:srs-arch. - Report the lookup, not only its outcome — the paths given, the words searched. What you say about a file is read off the file in that report and re-read before sending; that re-read is also where a figure of speech standing in for a plain verb comes out, and where a clause the reader cannot act on is deleted. Connected prose; a list only for what the reader counts. Every record named to a person is cited at its first mention in the message, from
python3 srs-dd/tools/srs_view.py --cite <ID>….
Two acts
Authoring ends at the written requirement; building it is a separate act, started deliberately, often by somebody else. This procedure is the second act; srs-new is the first. Sliding from one into the other leaves a specification that records only what shipped.
Building a requirement
In from a file (above), or from an approved requirement nobody built: python3 srs-dd/tools/srs_view.py --coverage, grep -rn "status: deferred" specs/; read it with its links both ways.
- The requirement still says what you are about to build. If not, you are authoring — stop,
srs-new. - The plan names requirements, not work — "fix the storage layer" is not a step — each cited at first mention from
--cite; constitution articlesART-*by number. The plan may not conflict with the method's articles or, where the project keeps one,specs/constitution.md. - Code.
- Name what you chose: where the requirement could have been met another way, the way taken goes to
specs/adr/(Workflow,srs-dd/standard.md), or the report says none. - Close the loop, in the same set of edits: re-read every named statement against what was built; what it does not describe is written in or taken out. A reworded statement passes the judgement
srs-newgives a new one, against the qualitiessrs-dd/standard.mdrequires of a statement, and the same lookup — what else speaks to it, what points at it, theFR-DOC-*sections and the files in itscodethat restate it — and the finding is said before the edit. Then status per Lifecycle,codeandtestswith real paths, and every file named there says so back withimplements:/verifies:above what carries it out, ended bysrs-end:(Annotations,srs-dd/standard.md): the field is the specification's claim, the annotation is the file's. An open issue the change settles leavesspecs/91-open-issues.md. python3 srs-dd/tools/srs_check.py, then thesrs-checkprocedure: suites offered, inspections named.
A fix that adds what the statement is silent about means the statement is wrong. A change naming no requirement means no behaviour moved or a requirement is missing.
Withdrawing a requirement
withdrawn cancels with no successor; with one, it is superseded and the successor is named. Before the status changes:
python3 srs-dd/tools/srs_view.py <ID>— the incoming links, grouped by field:depends_onloses its meaning,derives_fromits reason,refinesthe rule it sharpened,conflicts_withnothing.- Show the direct dependants in full, count what lies beyond; settle one level per decision — each resolution acts on the direct dependants, and may be a withdrawal with a tree of its own.
- Settle each dependant with the maintainer — none is a default: do not withdraw; narrow; supersede; cascade, each dependant back through this section; re-parent; promote and reword; orphan deliberately, and say so; stage it — intent, dependants, withdrawal last.
- Set the status and say why in the rationale, its only home. The number stays dead.
The checker flags what rests on a withdrawal — a guard, not a substitute.
Planning multi-requirement work
- Resolve the requirements in scope and their closure:
depends_on,derives_from,refines, and the incoming links. - Behaviour with no covering requirement: the first steps author it (
srs-new). - Order the steps by
depends_on; each step cites its requirements (--cite), the articles that bind it ("per SRS-DD-ART-030") and the verification method. - A
draftin scope is a blocker, marked so (SRS-DD-ART-020). Asupersededone sends the plan to its successor; awithdrawnone is an error to surface. - The last two steps, always: close the loop; the checker and the
srs-checkprocedure. A step that builds or tests is marked "requires the user's explicit confirmation each time" (SRS-DD-ART-030).
The plan lives in the conversation, never in specs/; a plan is not approval — statuses are (SRS-DD-ART-020).
Also
- Prohibitions: What not to do in
srs-dd/standard.md; and no builds or tests without the user's explicit confirmation (SRS-DD-ART-030). - What is put to the maintainer for a decision — a statement, a rewording, a step of a plan — is in the message that asks, as it would be written, never "as above".
- A mismatch between code and requirement: fix neither side; record it in
specs/91-open-issues.mdand tell the user. A finding ends in therefore — must be fixed; is deliberate, and why; needs the maintainer's decision, with the options. Without one it is an observation, and is worked out or dropped, not handed over.
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.

