agentleFS
kunalsurikunalsuri/ai-fication-kit/.claude/skills/implement-spec/SKILL.md

implement-spec

Skill3 starsChanged 4 months agoApache-2.0View on GitHub

Implement a spec from ai/lab/specs/ exactly as written — zero design decisions, stop-and-report on any spec-vs-reality conflict, tests are the definition of done. Built for lighter implementation models.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use implement-spec-with-codex, close-spec and 9 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.
  • dzhngSkill

    implement-spec-with-codex

    Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.

    Also in 4 projects that use this

  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 4 projects that use this

  • wolverin0Skill

    audit-decisions

    Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

    Also in 4 projects that use this

  • saffron-healthSkill

    get-pr-reviews

    Get nicely formatted output of the last review comments on a PR. Used internally by other skills.

    Also in 3 projects that use this

  • saffron-healthSkill

    push-everything

    Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.

    Also in 3 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 4 projects that use this

  • +4 more from dzhng

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 121 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the ENTIRE spec file, top to bottom, before writing any code.

    line 19
  2. Distinctive:

    Read any rationale/lessons-learnt doc the spec's preamble names — once.

    line 20
  3. Very specific:

    Read ai/guide/MODULE_MAP.md (Stability column) and ai/guide/CONVENTIONS.md.

    line 21
  4. Distinctive:

    Do NOT crawl the tree. Open other files only when the spec's touch list or your current step requires them.

    line 22
  5. Very specific:

    Every file in the spec's touch list marked "modify" exists.

    line 28
  6. Distinctive:

    If at ANY point the spec conflicts with what you find in the code, the docs, or a failing behaviour — the function signature differs, a …

    line 34
  7. Very specific:

    Do NOT pick the "obvious" interpretation.

    line 40
  8. Distinctive:

    Follow the spec's own ordering and any code skeleton it provides — structure, export names, and file layout are contractual, not …

    line 46
  9. Distinctive:

    If the spec has acceptance criteria, walk the list and mark each one explicitly: met / not met / blocked-on-question.

    line 60
  10. Very specific:

    NEVER flip [inferred] → [verified], and never edit an existing [verified] signature.

    line 73
  11. Very specific:

    If the spec implements a ai/lab/ROADMAP.md Planned feature, move its row from Planned to Shipped, cross-linking the spec, the WORKLOG row, …

    line 77

“Common” is measured: kept by at least 6 in 10 of the 121 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
<!-- Copyright (c) 2026 Kunal Suri (CEA LIST). All rights reserved. -->

Implement the spec at: $ARGUMENTS (If no path was given, ask for one and stop. Implement ONLY this spec.)

You are the implementer, not the designer. Every design decision has already been made in the spec. Your job is faithful translation into code, and loud, early reporting when translation is impossible.

Protocol (follow in order, no skipping)

0. Load context — exactly this, no more

  1. Read the ENTIRE spec file, top to bottom, before writing any code.
  2. Read any rationale/lessons-learnt doc the spec's preamble names — once.
  3. Read ai/guide/MODULE_MAP.md (Stability column) and ai/guide/CONVENTIONS.md.
  4. Do NOT crawl the tree. Open other files only when the spec's touch list or your current step requires them.

1. Pre-flight (all must pass before you write code)

  • npm test passes on the clean checkout (record the pass count).
  • node install.mjs verify . --strict passes.
  • Every file in the spec's touch list marked "modify" exists; confirm none is frozen or ? in MODULE_MAP.md. If one is → STOP AND REPORT.
  • Restate to yourself the spec's hard-constraints table (if present). Those constraints outrank your habits and your training priors.

2. THE PRIME RULE — stop-and-report, never improvise

If at ANY point the spec conflicts with what you find in the code, the docs, or a failing behaviour — the function signature differs, a file isn't where the spec says, an example contradicts a rule, a specified test cannot pass as written — you MUST stop and report:

  • the spec section, the file:line evidence, and the smallest question whose answer unblocks you. Do NOT pick the "obvious" interpretation. Do NOT patch around it. Do NOT widen scope to fix it. A wrong guess here costs more than the pause. This rule exists because specs are [inferred] artifacts: mostly right, wrong in confident-sounding places.

3. Implement

  • Follow the spec's own ordering and any code skeleton it provides — structure, export names, and file layout are contractual, not suggestions.
  • Touch ONLY files in the spec's touch list. No new dependencies unless the spec adds them. No drive-by refactors, renames, or "improvements".
  • License header on every new file, copied from a neighbouring file.
  • Match surrounding code style (imports, naming, error handling) over generic best practice.

4. Verify — the tests are the definition of done

  • Implement the spec's ENTIRE test plan (every numbered test), in the harness style the spec names. A test you cannot implement as specified is a §2 stop-and-report, not a skip.
  • npm test green (old count + new tests), node install.mjs verify . --strict clean. Paste real output; never summarize a test run you didn't execute.
  • If the spec has acceptance criteria, walk the list and mark each one explicitly: met / not met / blocked-on-question.

5. Review gate (the engineering loop's Review step — not optional)

  • Request /review-change on the completed diff in a FRESH context (a session that did not write the code), per ai/lab/specs/SPEC_engineering-loop.md. You implement; you do not approve your own work.
  • The review lands in ai/lab/reviews/ and its verdict is input to the human's merge decision — implementation "done" without a review is not loop-complete.

6. Knowledge updates (part of the change, not an afterthought)

  • Execute the spec's "knowledge update on completion" checklist. All new/changed rows and entries are tagged [inferred].
  • NEVER flip [inferred] → [verified], and never edit an existing [verified] signature. That is the human's move alone.
  • Append the WORKLOG entry linking spec, review, commits, and test evidence (verify scans these links — broken ones fail --strict).
  • If the spec implements a ai/lab/ROADMAP.md Planned feature, move its row from Planned to Shipped, cross-linking the spec, the WORKLOG row, and the PR.

7. Final report (in this order)

  1. Acceptance-criteria scorecard.
  2. Verbatim tail of npm test and verify --strict output.
  3. Deviations from the spec: list each one with its §2 report — the expected count is ZERO; anything else should already have stopped you.
  4. Files changed vs. the spec's touch list (must match exactly).
  5. Review status: link to the /review-change request/result for the human's merge decision.

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.