agentleFS
chohra-medchohra-med/expo_boilerplate/.claude/skills/spec-harness-install/SKILL.md

spec-harness-install

Skill34 starsChanged 5 months agoMITView on GitHub

Add or refresh Spec Harness in a repo — greenfield (new) or existing (integrate), idempotent. Use when Malik says 'install spec harness', 'set this repo up with spec harness', 'integrate spec harness into X', or 'start a new spec-harness project'. Runs the interview (mode, stack, constraints, work-intake source, learning goals, regression guards) and scaffolds the bank + agents + commands + skills without clobbering existing CLAUDE.md/AGENTS.md.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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
  1. Very specific:

    Every correction or FAIL cause goes through spec-harness-learn → a dated rule.

    line 19
  2. Distinctive:

    Never scaffold the second-brain vault.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

spec-harness-install

Stand the system up in a target repo. Prefer the script: bash <spec-harness>/bin/sh-install.sh <target> [new|integrate] <name>. Then run the interview to fill the bank + frequent_rules from the real stack (never copy another stack's rules). Integrate mode: run index first to ground in real code.

Run it

  1. Load the full procedure — read the command doc and follow it exactly: .claude/commands/spec-harness/init.md (this repo) or the spec-harness source commands/init.md.
  2. Agents — spawn from .claude/agents/: researcher.
  3. Stay inside the 3 pillars — memory bank ( .memory/) · Spec-Driven Development · Harness (ratchet AGENTS.md + verifier + learning loop). Read SPEC-HARNESS.md for how this repo is wired.

Non-negotiables

  • The ratchet only tightens (rules are append/sharpen, never drop).
  • Nothing is "done" until the separate verifier returns PASS against goal.md.
  • Every correction or FAIL cause goes through spec-harness-learn → a dated rule.
  • Never scaffold the second-brain vault. Never commit a client repo unless asked.

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.