agentleFS
CRELLIA-S-LCRELLIA-S-L/srs-dd/.claude/skills/srs-baseline/SKILL.md

srs-baseline

Skill0 starsChanged 32 days agoMITView on GitHub

Freeze this project's specification as a baseline — read what changed since the last one, agree the version with the maintainer, then run srs-dd/tools/srs_baseline.py, which writes the row into specs/92-baselines.md. Invoke when the user asks to cut, freeze, record or tag a baseline of the specification, or at a milestone worth being able to compare against later. The commit, and any spec/v* tag, stay with the maintainer's git client.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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
  1. Distinctive:

    Read step 1 against it and say which reading you used, out loud — "MINOR, because two requirements were added and none removed".

    line 37
  2. Distinctive:

    Do not settle it yourself.

    line 39
  3. Distinctive:

    Read it: where it says something the diff in step 1 did not, one of the two is wrong, and finding out which is cheaper now than after the …

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- Copyright (c) 2026 CRELLIA S.L. — part of SRS-DD, distributed under the MIT License -->

Freezing a baseline

A baseline is a row in specs/92-baselines.md and the commit that adds it. The rules are in the Baselines section of srs-dd/standard.md; read it if you have not in this session. The command writes the row. What it will not decide is the number that row carries, and it deliberately stops before the commit.

Procedure

  1. Read what changed since the last baseline. The newest version in specs/92-baselines.md is the one to compare against:

    python3 srs-dd/tools/srs_view.py --diff <that version>

    A version, not a tag: a baseline need not have one. Show the user what comes back — requirements added, removed, reworded, each named as AGENTS.md asks at its first mention, which python3 srs-dd/tools/srs_view.py --cite <ID>… prints. A column of bare numbers is the one thing this list must not be: it is the last look before the freeze. This is what the baseline is about to freeze, and it is the last moment to notice something in it that was not meant to be frozen yet.

  2. Offer an audit of what is about to be frozen. The diff from step 1 names it: the requirements added and reworded, and the ones they link to. A baseline is the last cheap moment — after it, the frozen state is what every reader compares against, and a statement nobody can test freezes exactly as well as a good one.

    Scoped to what the diff names, never the whole specification: an audit of everything at every baseline is the step people stop taking. The procedure is srs-audit; offer it and accept a no.

  3. Propose the version, and let the maintainer settle it. The scheme is in the Baselines section of srs-dd/standard.md. Read step 1 against it and say which reading you used, out loud — "MINOR, because two requirements were added and none removed".

    Do not settle it yourself. The number is a claim about the specification, and the person who owns the project owns that claim.

  4. Write the row.

    python3 srs-dd/tools/srs_baseline.py X.Y.Z --dry-run
    python3 srs-dd/tools/srs_baseline.py X.Y.Z

    The dry run prints the row and writes nothing. Read it: where it says something the diff in step 1 did not, one of the two is wrong, and finding out which is cheaper now than after the commit.

  5. Hand the commit back. The command writes specs/92-baselines.md, the checker it ran may have refreshed specs/90-traceability.md beside it, and there it stops — nothing is committed, tagged or pushed. Say which files are waiting and that the commit carrying them is the baseline; the maintainer makes it with whatever git client this project is driven by.
  6. Offer the tag once. spec/vX.Y.Z on that commit makes the baseline easy to name in git later. Nothing depends on it — where there is none, the baseline is found by the commit that added its row. Mention it and move on; do not turn it into a step.

When it refuses

Exit code 2, before the row is written: a malformed version, a missing log or one with no table, a version the log already records, or an error from the checker. A warning does not stop it; the Baselines section of srs-dd/standard.md says on what terms, and why. Fix the cause and run it again — there is nothing to clean up, and nothing in the history was touched.

What this procedure does not do

Commit. Tag. Push. Choose the version. Cut a release — that is a separate act with its own number, and in this repository's own case its own framework-only procedure; a baseline freezes what the system must do, a release ships what it does.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.