implement
Skill0 starsChanged 3 months agoMITView on GitHub
Implement one ticket with TDD at seams, type checking, tests, code-review, then commit. Called by wayfinder for each implementation ticket. The per-ticket quality gate replaces the old final review pass.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- revisit-studies/studytheir own version, first seen Nov 9, 2026
- dz114879/skillstheir own version, first seen Nov 8, 2026
- Dimon94/dveritytheir own version, first seen Nov 8, 2026
- Dimon94/skillstheir own version, first seen Nov 8, 2026
- The-Vibe-Company/quivrtheir own version, first seen Nov 8, 2026
- miklschmidt/archboardtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use setup-ts-deep-modules, ask-matt and 6 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.
liufeng1976Skillsetup-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
GoogleSkillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Also in 91 projects that use this
RoentekSkillloop-me
Grill me about specs for the workflows I want to build, within this workspace.
Also in 50 projects that use this
AWSSkillto-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
ryotaroh180105Skillclaude-handoff
Hand the current conversation off to a fresh background agent that picks up the work immediately.
Also in 42 projects that use this
LesaniSkillwriting-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
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- mattpocock/skills★ 309ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- foambubble/foam★ 17ksame name
- formbricks/formbricks★ 13ksame name
- ArcReel/ArcReel★ 6.3ksame name
- vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
- fallow-rs/fallow★ 5.3ksame name
- withcoral/coral★ 4.9ksame name
- bestofjs/bestofjs★ 3.1ksame name
181 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 repository19 other files it gives its agents.
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- document-directorySkill
- domain-modelingSkill
- grillingSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- prototypeSkill
- researchSkill
- resolving-merge-conflictsSkill
- scope-lockSkill
- setupSkill
- start-sessionSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- wayfinderSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 171 edited versions we read keep these.
8
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
- Distinctive: line 16
Red: Write a failing test at a pre-agreed seam (public interface).
- Distinctive: line 20
Green: Write the smallest honest implementation that makes the test pass.
- Distinctive: line 46
Red before green: No implementation before its test exists and fails for the right reason.
- Distinctive: line 48
Green means smallest honest implementation: No stubbing the behavior under test.
- Distinctive: line 69
Never skip tests at agreed seams.
- Distinctive: line 70
Never commit without the full test sweep passing.
- Distinctive: line 71
Never skip code review before committing.
- Distinctive: line 72
Never write a test that can't actually fail.
“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.
Files
Implement
Implement one ticket. This is the per-ticket implementation cycle, called by wayfinder for each ticket in the breakdown.
Process
- Confirm the ticket is unblocked — its dependencies (if tracked) are done. If not, report back to wayfinder to pick a different one.
- Red. Write a failing test at a pre-agreed seam (public interface). Confirm it fails for the expected reason, not an unrelated error.
- Green. Write the smallest honest implementation that makes the test pass. No hardcoding expected output.
- Type check regularly throughout implementation.
- Run tests — the specific test file as you work, then a full test sweep at the end. Evidence gate: the ticket is not done until you paste the actual green test/command output. Asserting "tests pass" without the output does not advance the ticket.
- Invoke
skills/code-review/SKILL.mdto review the work. - Commit the work to the current branch. One commit per completed ticket with a message describing what it delivers.
- Update tracking — mark the ticket as done in the configured tracker.
TDD discipline
Uses /codebase-design vocabulary for seam placement: accept
dependencies don't create them; place seams at volatile boundaries;
the interface is the test surface.
- Tests verify behavior through seams — pre-agreed public interfaces and boundaries. Never test implementation internals.
- Red before green. No implementation before its test exists and fails for the right reason.
- Green means smallest honest implementation. No stubbing the behavior under test.
Reference: skills/tdd/SKILL.md for the full TDD
discipline (red→green, anti-patterns).
Anti-patterns (never do these)
- Implementation-coupled tests (testing private methods, internal state).
- Tautological assertions (mock wired to be called, then asserted).
- Horizontal slicing within a ticket.
- Skipping the code-review step.
Bundled skill references
skills/tdd/SKILL.md— TDD discipline referenceskills/codebase-design/SKILL.md— vocabulary for seam placement and interface depth
What this skill must never do
- Never skip tests at agreed seams.
- Never commit without the full test sweep passing.
- Never skip code review before committing.
- Never write a test that can't actually fail.
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.