implement-task
Skill2 starsChanged 4 months agoMITView on GitHub
Executes ONE task from a spec's plan with strict TDD protocol (F6 Construction). Use to implement tasks one at a time.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- allemaar/open-skillstheir own version, first seen Nov 8, 2026
- etr/groundworktheir own version, first seen Nov 8, 2026
- rumotion/ai-agent-project-templatetheir own version, first seen Nov 1, 2026
- allanbian1017/skillstheir own version, first seen Nov 1, 2026
- berkekcay/link-shortener-agent-readytheir own version, first seen Oct 25, 2026
- juanitourquiza/shipframetheir own version, first seen Oct 23, 2026
Used with
Projects with it also use handoff and code-review.
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.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- ModelEngine-Group/fit-framework★ 2.1ksame name
- etr/groundwork★ 45same name
- dirumahrafif/my-opencode-skills★ 37same name
- allemaar/open-skills★ 15same name
- asta-nguyen/kamehadb★ 14same name
- phatysddev/skills★ 8same name
- asta-nguyen/agent-devkit★ 4same name
- juanitourquiza/shipframe★ 4same name
- allanbian1017/skills★ 2same name
- jersson/jenie-ai-tools★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- as-is-learnSkill
- as-isSkill
- as-is-syncSkill
- clarifySkill
- consistencySkill
- context-reportSkill
- convergeSkill
- harness-initSkill
- orchestrateSkill
- repo-addSkill
- repo-mapSkill
- spec-createSkill
- spec-reviewSkill
- system-mapSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Read the full spec: the task is implemented against its acceptance criteria, not against your interpretation.
- Distinctive: line 26
If the task reveals ambiguity in the spec: STOP and escalate.
“Common” is measured: kept by at least 6 in 10 of the 14 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.
Files
Implement ONLY task $1 from spec $0. Protocol:
- Harness startup: read harness/claude-progress.md and
git log --oneline -10; run ./harness/init.sh and verify with a smoke test that the environment works BEFORE touching anything. - Read the full spec: the task is implemented against its acceptance
criteria, not against your interpretation. Also load the context pack
of the task's repo (
<prefijo>-<repo>; the system one if the task crosses repos) — its "Pitfalls" exist so you don't repeat them. - TDD: write the tests that encode the criteria → verify they FAIL → commit the tests → implement until green WITHOUT touching the tests → refactor.
- End-to-end verification of the functionality as a user would do it; only then update "passes" in harness/feature_list.json. FORBIDDEN to edit or delete feature descriptions from that file.
- Clean closure: lint + typecheck green, commit with Conventional Commits referencing the spec, and an entry in harness/claude-progress.md (what was done, decisions, what's next).
If the task reveals ambiguity in the spec: STOP and escalate. Do not improvise scope. If you discover unplanned work, note it as a new task in the spec instead of doing it now.
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
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.