agentleFS
Sign inStart free
maidepsmaideps/ai-harness-framework/skills/adopt/SKILL.md

adopt

Skill2 starsChanged 6 days agoMITView on GitHub

Bootstrapping the harness in a new project — placing templates per the manifest mapping and declaring product roots.

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-stories, story-done and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    create-stories

    Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

    Also in 11 projects that use this

  • lilangMaxSkill

    story-done

    End-of-story completion review. Reads the story file, verifies each acceptance criterion against the implementation, checks for GDD/ADR deviations, prompts code review, updates story status to Complete, and surfaces the next ready story from the sprint.

    Also in 11 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 25 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Place each template at its declared destination — the manifest's templates entries carry the mapping machine-readably:

    line 18
  2. Very specific:

    Add project-specific architecture rules to .harness/arch-rules.json.

    line 25
  3. Very specific:

    Run ./init.sh, then npm run check — the project is now on the harness.

    line 26
  4. Distinctive:

    Never overwrite existing project files with skeleton content.

    line 30

“Common” is measured: kept by at least 6 in 10 of the 25 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Adopt

Bringing the harness into a new or existing project.

When to Use

  • Setting up a fresh repository with the harness
  • Re-syncing a project after a harness upgrade
  • Auditing whether the seam contract is satisfied

Workflow

  1. Copy the CORE files and templates/ into the repository. CORE ships as-is (AGENTS.md, CLAUDE.md, Makefile, package.json, init.sh, scripts/, skills/, templates/, .harness/).
  2. Place each template at its declared destination — the manifest's templates entries carry the mapping machine-readably:
    • { "from": "templates/LICENSE", "to": "LICENSE" } → copy the MIT starter once; the adopter's LICENSE is preserved by upgrades.
    • { "from": "templates/progress.md", "to": "PROGRESS.md" } → copy there, then run node scripts/framework-check.mjs progress-update after customizing features.
    • { "from": "templates/nvmrc", "to": ".nvmrc" } → copy there and adjust the project Node version if needed.
    • { "from": "templates/sprint-contract.md", "keep": true } → stays under templates/ as reference material.
  3. Fill the skeletons: replace placeholder content with this project's real description, architecture, and standards. The lint layer fails while placeholder text remains — that is intentional.
  4. Declare product-owned directories in the manifest's productRoots (e.g. "src/", "packages/") so arch-005 exempts them from classification.
  5. Add project-specific architecture rules to .harness/arch-rules.json.
  6. Run ./init.sh, then npm run check — the project is now on the harness.

Rules

  • Never overwrite existing project files with skeleton content.
  • Any repository layout change updates the manifest and docs/ARCHITECTURE.md in the same commit.
  • CORE files must not be edited; project skills may be added under skills/.

Quick Reference

  • CORE + templates copied
  • Templates placed per the manifest {from, to} mapping
  • Skeletons filled (no placeholder text)
  • productRoots declared for product code
  • ./init.sh and npm run check pass

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.

Check your setup, free