agentleFS
caterpi11arcaterpi11ar/giclaw/.agents/skills/implement-spec/SKILL.md

implement-spec

Skill9 starsChanged 29 days agoNo licenceView on GitHub

Implement the result of /to-spec and /to-tickets in code.

130 other projects use a version of this, 70 of them edited; 57 of 70 edited versions we compared changed its rules; 8 new projects in the last 4 weeks, against 2 the 4 before.

How people change it

57 of 70 edited versions changed its rules, and some changes recur.

Of the 70 edited versions we compared: 10 keep every rule, 3 are an older text, 57 made changes of their own.

Not in older versions

  1. A rule we can't quote: its licence doesn't allow itmissing from 2 of 3
  2. A rule we can't quote: its licence doesn't allow itmissing from 1 of 3
  3. A rule we can't quote: its licence doesn't allow itmissing from 1 of 3

Rules people drop

  1. A rule we can't quote: its licence doesn't allow itdropped by 21 of 57
  2. A rule we can't quote: its licence doesn't allow itdropped by 7 of 57
  3. A rule we can't quote: its licence doesn't allow itdropped by 6 of 57
  4. A rule we can't quote: its licence doesn't allow itdropped by 6 of 57
  5. A rule we can't quote: its licence doesn't allow itdropped by 4 of 57

Rules people add

  1. Start every subagent with a fresh context window.added by 32 of 57
  2. Create a branch, and a draft PR. The PR should be marked as 'closing' the spec issue and tickets.added by 15 of 57
  3. A rule we can't quote: its licence doesn't allow itadded by 2 of 57
  4. A rule we can't quote: its licence doesn't allow itadded by 2 of 57
  5. A rule we can't quote: its licence doesn't allow itadded by 2 of 57

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 8 new projects took it in the last 4 weeks, 4× the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 1 new projectWeek of Oct 11: 1 new projectWeek of Oct 18: 1 new projectWeek of Oct 25: 2 new projectsWeek of Nov 1: 3 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 10 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use implement-spec-with-codex, audit-decisions 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.
  • 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

    audit-decisions

    Audit the decisions an implementing agent made, not its diff — a pure audit that traces the session's history into a decisions ledger, changes no code, and never blocks an unsupervised run. Working code still embeds architecture the user never chose; surface it because future work inherits it. Use when the user wants to review the decisions the AI made on their behalf, before merging or committing AI-implemented work, when integrating a delegated subagent's pass, or when a fix "works" but might be a point fix.

    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

  • +8 more from dzhng

The file

We split this skill into the rules it gives an agent

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

  • 4

    Common

    Most of the 104 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.