agentleFS
Sign inStart free
cekrauseeecekrauseee/harness/skills/implement/SKILL.md

implement

Skill0 starsChanged 13 days agoMITView on GitHub

Implement a requested software change using the application's conventions and relevant acceptance criteria.

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 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.
  • 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

    to-spec

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 168 projects that use this

  • +3 more from google

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 171 edited versions we read keep these.

  • 2

    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:

    Keep scaffolds limited to current requirements: remove unused demo content, placeholders, and generated features together with their unused …

    line 12
  2. Distinctive:

    Use the current plan when it helps.

    line 14

“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

Understand the behavior to change and the relevant application boundaries. Follow the project's established architecture, naming, and design patterns. Make routine implementation choices within the request; surface a material conflict or scope change without abandoning independent authorized work.

Choose the simplest complete solution. Reuse suitable project code, platform features, and existing dependencies before adding new ones. Organize modules and components around cohesive responsibilities (SRP), and share logic that represents the same behavior (DRY). Let actual use justify abstractions, layers, and extension points. Judge simplicity by readability, correctness, and maintenance cost.

Keep scaffolds limited to current requirements: remove unused demo content, placeholders, and generated features together with their unused references and dependencies. Use current, idiomatic practices compatible with the project's supported technology versions; verify version-sensitive choices against official documentation.

Use the current plan when it helps. Make targeted changes, preserve unrelated user work, and keep internal work IDs, agent topology, plans, and debugging residue out of product code and remote-facing artifacts. Do not turn a local finding into an unrelated refactor.

Validate observable behavior according to the test skill and the risk of the change. Resolve failures caused by the requested work and rerun affected checks. Preserve useful execution context through Harness tools; promote durable knowledge separately through memory capture.

For every development task, use document and development experience to assess and maintain the project's documentation, DX, and local/remote CI as acceptance criteria. Preserve compliant project setup and complete missing or outdated requirements. Separate independent remediation into coherent deliveries when appropriate; a separate PR does not satisfy a pending criterion. Use git when preparing commits or PRs.

Finish the requested deliverable, including its required integration and verification. Report the outcome, evidence, and material limitations in the user's language.

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