agentleFS
kyoo-147kyoo-147/MinimalShip/skills/engineering/implement/SKILL.md

implement

Skill0 starsChanged 24 days agoMITView on GitHub

Build one accepted product slice from a spec or bounded work item and close it with evidence.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

  • 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

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 47 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 172 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before editing, confirm that the feature is approved in RUN.md or that the user explicitly authorized implementation.

    line 7
  2. Distinctive:

    Read the relevant code, tests, glossary, ADRs, and package scripts.

    line 12
  3. Distinctive:

    Run focused tests, typechecks, lint, build, and one realistic smoke path as applicable.

    line 15
  4. Very specific:

    Call code-review before committing when the change is more than trivial.

    line 17

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

Before editing, confirm that the feature is approved in RUN.md or that the user explicitly authorized implementation. If the request is still in planning, stop after updating FEATURES.md and RUN.md and present the proposal.

Implement

  1. Pin the accepted spec or work item and confirm the current branch.
  2. Read the relevant code, tests, glossary, ADRs, and package scripts.
  3. Choose the smallest public seam and call tdd when tests improve confidence.
  4. Implement a vertical slice with no unrelated refactor or dependency.
  5. Run focused tests, typechecks, lint, build, and one realistic smoke path as applicable.
  6. Review the diff for scope, secrets, regressions, and missing acceptance evidence.
  7. Call code-review before committing when the change is more than trivial.

Report PASS, FAIL, or BLOCKED per acceptance case. A successful compile is not proof of a working product.

On completion, move the feature to VERIFYING, record exact evidence in RUN.md, and mark it DONE only when every acceptance criterion passes. A failed or unexecuted check keeps it out of DONE.

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.