build-feature
Skill565 starsChanged 5 days agoMITView on GitHub
Builds a new tool, parameter or behaviour in thin test-first slices, after settling the open decisions with the owner. Use when asked to "add", "build", "implement", "support" or "create" something, such as a new tool or a new tool parameter.
17 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- Slama-Consulting/proofbenchtheir own version, first seen Nov 15, 2026
- cluaiz/cluaiz-toolstheir own version, first seen Nov 15, 2026
- todoist/todoist-cliedited, first seen Nov 15, 2026
- seanmcgary/claude-skillstheir own version, first seen Nov 11, 2026
- Doist/todoist-cliedited, first seen Nov 8, 2026
- sbradl/claude-skillstheir own version, first seen Oct 15, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- Doist/todoist-cli★ 33241% same
- todoist/todoist-cli★ 33241% same
Wrote their own version · 15
- signerlabs/ShipSwift★ 3.3ksame name
- AlemTuzlak/skills★ 45same name
- Guild-Agents/guild★ 4same name
- cluaiz/cluaiz-tools★ 3same name
- garthcodes/claude-skills★ 2same name
- MaximSTH/meta-layer-starter★ 2same name
- zyggy-org/zyggy★ 2same name
- evgenii-studitskikh/Claude-Code-SaaS-Studio★ 1same name
- sirakinb/claude-code-skills★ 1same name
- Slama-Consulting/proofbench★ 1same name
5 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fix-bugSkill
- learnSkill
- refactorSkill
- review-changesSkill
- verifySkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
0
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
- Very specific: line 18
Write each behaviour as an input and the expected output, for example: "update-tasks with deadlineDate: "remove" sends deadlineDate: null …
- Very specific: line 41
Follow verify. If the feature needs restructuring first, do that as a separate change with refactor.
“Common” is measured: kept by at least 6 in 10 of the 16 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
Build a feature
1. Read the closest existing feature
Find the tool most like the one you are building and read it with its test: src/tools/add-projects.ts for a batch write, src/tools/find-tasks.ts for a read, src/tools/update-tasks.ts for an update. Read the rules in AGENTS.md ("Tool Schema Design Rules", "Adding a New Tool"). Done when you can name the file you will copy patterns from.
2. Settle decisions in one round
List what the request leaves open: naming, input shape, what to return, error cases, annotations (readOnlyHint, destructiveHint, openWorldHint), whether it needs a routing line in src/mcp-server.ts. Ask the owner all of them at once, each with your recommendation. Don't ask what the code can answer. Done when every decision has an answer.
3. Write "done" as checkable behaviours
Write each behaviour as an input and the expected output, for example: "update-tasks with deadlineDate: "remove" sends deadlineDate: null to updateTask". Each becomes a test. Done when a test could pass or fail on every one.
4. Build in thin slices, test first
For each behaviour: write its test at the public interface (<tool>.execute(args, mockTodoistApi)), see it fail, make it pass, run its test file. Follow write-tests. Done when every behaviour from step 3 has a passing test you saw fail.
5. Update everything the change touches
| You changed | Also update |
| Added a tool | src/utils/tool-names.ts, src/tool-registry.ts, src/index.ts (named exports), src/tools/tool-annotations.test.ts |
| A tool writes a list of items | Per-item failures (see "Batch write tools" in AGENTS.md); batch-failures-contract.test.ts checks it |
| A clearable optional field | The "remove"/"unassign" string, both runtime branches, the schema description |
| Tool or field descriptions | npm run eval -- --label before, then --label after; diff tmp/eval/*.json (paid models: ask first) |
| The tool surface grew | src/token-footprint.test.ts may fail: raise DEFAULT_TOKEN_BUDGET only if needed, and say so in the PR |
| Cross-tool routing | The instructions string in src/mcp-server.ts, only if a model needs it to pick between tools |
| Output schemas | src/utils/output-schemas.ts; never .nullable() (output-schema-nullability.test.ts) |
| Structure (new folder or helper) | CODEBASE.md, by its "Keeping CODEBASE.md accurate" rules |
Done when each row that applies is handled.
6. Verify and report
Follow verify. If the feature needs restructuring first, do that as a separate change with refactor.
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.

