agentleFS
Sign inStart free
NagiliantNagiliant/Genesis-Legacy-V2/skills/genesis-implement/SKILL.md

Implement

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Implement one micro spec — one commit, one PR. The micro spec is the complete instruction set; write only the files in its File Operations table, verify against its acceptance criteria, commit.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-ts-deep-modules, ask-matt 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.
  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 43 projects that use this

  • GoogleSkill

    ask-matt

    Ask which skill or flow fits your situation. A router over the skills in this repo.

    Also in 91 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 50 projects that use this

  • AWSSkill

    to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

    Also in 88 projects that use this

  • ryotaroh180105Skill

    claude-handoff

    Hand the current conversation off to a fresh background agent that picks up the work immediately.

    Also in 42 projects that use this

  • GoogleSkill

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 168 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Verify: run the project's build / test / lint commands as declared in the constitution, and confirm the spec's acceptance criteria pass.

    line 27

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

Implement — One Spec, One Commit, One PR

Implement exactly one micro spec per invocation. The micro spec is the complete instruction set — no task selection, no group management. Write the code/content for the files in its File Operations table, verify against its acceptance criteria, then commit.

Gate: the active group's micro specs are written and the prior phase is accepted. Followed by the A1–A5 audits once the group's specs are all implemented.

Inputs

  • The single target micro spec at .genesis/features/<feature>/micro-specs/{spec-id}.md (the complete instruction set).
  • .genesis/project-state.md (mode), the constitution, northstar.md.
  • approvals/master.json / approvals/group-<N>.json for position.
  • The files listed in the spec's reads interface.

Process

  1. Pre-flight: confirm the feature/group/spec and that the prior phase is accepted; read the target spec in full.
  2. Implement (mode-branched):
    • Greenfield: implement the files in the File Operations table; satisfy every FR/AC; write tests per the constitution.
    • Brownfield: stay strictly within the spec's File Operations table (scope discipline); preserve existing behavior; classify any touched code inherited vs introduced via git blame; ensure no regressions.
    • Lowfield: produce the stage's artifacts per the declared artifact schema; verify the schema validates.
  3. Verify: run the project's build / test / lint commands as declared in the constitution, and confirm the spec's acceptance criteria pass. Do not write outside the spec's File Operations table.
  4. Finalize: one commit scoped to the spec (implement: {spec-id} — {title}), then open one PR. Log any failed approaches to tried.json so they are not retried.

Anti-laziness

What you write runs. No stubs, no TODO, no "simplified version," no narrowing the spec to dodge it. A change is not done at the first file — sweep the blast radius named in the File Operations table (callers, types, tests, configs). If the spec cannot be satisfied as written, stop and surface why — do not ship a partial.

Output

  • The source files / content artifacts named in the spec's File Operations table.
  • One commit + one PR.
  • (Optional) a tried.json entry recording failed approaches.

Next step

Implement the next spec, or — when the group's specs are all done — run /genesis-a1.

Natural language triggers

- "implement spec 1.3"
- "build this micro spec"
- "implement the next spec"

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