agentleFS
Sign inStart free
chinkanchinkan/RustFox/.agents/skills/implement-spec/SKILL.md

implement-spec

Skill11 starsChanged 41 days agoMITView on GitHub

Implement a specification in code.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 76 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Implementer subagents: should be run in the background where possible for maximum concurrency.

    line 15
  2. Distinctive:

    Read the spec and tickets.

    line 19
  3. Distinctive:

    Create a branch, and a draft PR.

    line 23
  4. Distinctive:

    Use implementer subagents to implement each ticket.

    line 25
  5. Distinctive:

    If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets.

    line 29

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

You have been provided a spec. This spec should have tickets associated with it, describing how to implement the spec.

The goal is a PR which implements the entire spec on a single branch.

The tickets are not a list of steps. They are a task graph with blocking relationships between them. This means there is always a frontier of tickets which are ready to be grabbed.

Communication to and from subagents should be sparse. Communicate primarily through context pointers: to the spec, tickets, research notes, and previous commits. Don't duplicate information already available via pointers.

Implementer subagents should be run in the background where possible for maximum concurrency.

Steps

  1. Read the spec and tickets. Read enough to understand the task graph.
  2. (optional) Use an exploration subagent to conduct any exploration required by the tickets - relevant codebase files or external documentation. Ensure the exploration subagent can save files - it should save its markdown notes in a directory outside the repo, accessible by all future subagents. This lets implementer subagents focus on implementation rather than exploration.
  3. Create a branch, and a draft PR. The PR should be marked as 'closing' the spec issue and tickets.
  4. Use implementer subagents to implement each ticket. Each implementer subagent should work in its own worktree, on its own branch.
  5. Once an implementer subagent completes, merge its work to the PR branch with a merger subagent.
  6. If this changes the frontier of available tickets, kick off more implementer subagents to work on the new tickets. This allows for maximum concurrency.
  7. Once all tickets are complete, run /code-review on the PR branch. Fix all issues raised by the code review in a single implementer subagent.
  8. Mark the PR as ready for review.
  9. Clean up all implementer subagent worktrees.

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.

Reviews can't be read right now.

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