agentleFS
Sign inStart free
YassimbaYassimba/loom/skills/implement/SKILL.md

implement

Skill9 starsChanged 2 months agoApache-2.0View on GitHub

Implement a piece of work based on a spec or set of tickets.

191 other projects use a version of this, 62 of them edited.

Adopted by

Most recently taken up by

Used with

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

    resolving-merge-conflicts

    Use when you need to resolve an in-progress git merge/rebase conflict.

    Also in 83 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 1

    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. Very specific:

    Run bv --robot-next; never run bare bv.

    line 12
  2. Very specific:

    Verify the returned ticket is open, ready, and unassigned with br show <id> --json.

    line 13
  3. Distinctive:

    Read the claimed ticket fully and treat its body as the request.

    line 15
  4. Very specific:

    Before coding, use blueprint to show the design and get approval.

    line 19
  5. Very specific:

    Use tdd where useful at pre-agreed seams.

    line 21
  6. Very specific:

    When implementation is complete, invoke code-review.

    line 23

“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 the work supplied by the user. If they supplied no spec or ticket, take the next actionable ticket from the project's documented tracker and use it as the scope.

For Beads:

  1. Confirm .beads/, br, and bv exist.
  2. Run bv --robot-next; never run bare bv.
  3. Verify the returned ticket is open, ready, and unassigned with br show <id> --json.
  4. Claim it atomically with br update <id> --claim. If another actor wins, repeat from step 2.
  5. Read the claimed ticket fully and treat its body as the request. If no actionable ticket exists, report that and stop.

Invoke ponytail and reuse as much existing code as possible.

Before coding, use blueprint to show the design and get approval. Skip it only for trivial changes such as a rename or one-line fix.

Use tdd where useful at pre-agreed seams. A ticket's Rules & Examples map is the scenario list: one test per example.

When implementation is complete, invoke code-review.

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