agentleFS
chrille0313chrille0313/agentic-monorepo-template/.claude/skills/build/SKILL.md

build

Skill4 starsChanged 3 months agoMITView on GitHub

Run the inner agentic loop on one task. The implementer builds, a fresh-context reviewer judges, and findings cycle back until approval (max 3 rounds). Use when the user says "build X", "implement issue #N", "work on the next backlog item", or CI dispatches a labeled issue.

169 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances 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.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • TrevokeSkill

    define

    Use when a new feature request, bug report, or work request needs requirements defined before implementation

    Also in 3 projects that use this

  • HAR5HA-7663Skill

    shape

    Plan the UX and UI for a feature before writing code. Runs a structured discovery interview, then produces a design brief that guides implementation. Use during the planning phase to establish design direction, constraints, and strategy before any code is written.

    Also in 6 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 155 edited versions we read keep these.

  • 4

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    No acceptance criteria obtainable → stop and ask the user.

    line 16
  2. Very specific:

    If not already on a task branch/worktree: create branch agent/<short-slug> (worktree if the session supports it).

    line 20
  3. Very specific:

    If the task is an issue, label it in-progress now.

    line 22
  4. Distinctive:

    No-progress exit: if the round produced the same blocking findings as the previous one, or the diff didn't change, stop early and escalate.

    line 35
  5. Distinctive:

    After round 3 still not approved → stop and escalate: present the spec, what was built, and the unresolved findings.

    line 37
  6. Very specific:

    Commit on the task branch following the commit skill: small modular commits, referencing the source issue.

    line 43
  7. Distinctive:

    Never merge. The merge gate is human.

    line 50

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

/build: the inner loop (evaluator-optimizer)

Input ($ARGUMENTS): an issue number, a task description, or empty (meaning the next ready backlog item).

You are the loop controller. You do not implement or review yourself; you dispatch the implementer and reviewer subagents, own the command-contract gate, route the verdict, and own git state.

1. Resolve the spec

  • Issue number → gh issue view <n> (body + comments).
  • Description or empty → if it already has acceptance criteria, use it; otherwise spawn the pm agent to shape it into a spec (for empty input, PM also picks the item).
  • No acceptance criteria obtainable → stop and ask the user; never build without a spec.

2. Prepare isolation

If not already on a task branch/worktree: create branch agent/<short-slug> (worktree if the session supports it). Never build on main.

If the task is an issue, label it in-progress now; remove the label when the loop ends (PR opened, or escalation).

3. Loop (max 3 rounds)

Round N:

  1. Implement: spawn the implementer agent with the full spec text. On round 2+, message the same implementer (it has the context) with the reviewer's blocking findings verbatim.
  2. Sanity-check its report: if STATUS: BLOCKED, stop and surface it to the user.
  3. Gate: run check/test/build yourself on the finished diff. You own this run: the implementer checks only what it touched, and the reviewer takes your result as given. Red goes back to the implementer without consuming a round, at most twice in a row; a third red gate ends the loop the way STATUS: BLOCKED does, with the failing output surfaced.
  4. Review: spawn a fresh reviewer agent each round (never reuse; fresh context is the point). Give it only the spec, the branch/diff reference, the round number, and the gate result. Never forward the implementer's report or reasoning.
  5. Route the verdict:
    • APPROVE → exit loop to step 4.
    • REQUEST_CHANGES → next round with the blocking findings.
    • No-progress exit: if the round produced the same blocking findings as the previous one, or the diff didn't change, stop early and escalate; more rounds provably won't help.
    • Disputed finding: when the implementer disputed a finding with evidence and a reviewer restates it, surface the disagreement to the user if interactive. If headless, spawn a fresh judge agent (general-purpose) with only the spec, the finding, and both sides' evidence; its ruling on that finding is final. Never let the implementer and reviewer negotiate to consensus.
    • After round 3 still not approved → stop and escalate: present the spec, what was built, and the unresolved findings. Do not keep looping; do not merge anything.

4. On approval

Your gate already ran green on the approved diff, and CI runs it again on the PR.

  1. Commit on the task branch following the commit skill: small modular commits, referencing the source issue.
  2. Interactive session → present a summary and ask whether to push + open a PR. Headless/CI session → push and open a PR, Closes #<n> in the body, and comment the PR link on the issue.
  3. The summary/PR body must make the human gate an informed check, not a rubber stamp:
    • what was built, mapped to the acceptance criteria
    • review-round history: findings by severity, fixed vs disputed
    • verification evidence: the gate result, and what the reviewer exercised on the running app
  4. Never merge. The merge gate is human.

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.