implement-feature
Skill1 starsChanged 4 months agoMITView on GitHub
Add or change a feature in the researcher-harness following the project constitution (design note → implement → tests → acceptance). Use for any non-trivial change to code under src/harness/.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- Disthere/agentic-openspectheir own version, first seen Nov 16, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- tddworks/ClaudeBartheir own version, first seen Nov 3, 2026
- snuffish/dotfilestheir own version, first seen Nov 1, 2026
- mAzurkovic/skillstheir own version, first seen Nov 1, 2026
- olimstv/claude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use prepare-release, create-skill 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.
ShopifySkillprepare-release
Prepare the changeset-release/main branch for release by syncing version.ts files and running pnpm install
Also in 3 projects that use this
ElasticSkillcreate-skill
Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.
Also in 3 projects that use this
MicrosoftSkillplaywright-cli
Automate browser interactions, test web pages and work with Playwright tests.
Also in 3 projects that use this
VercelSkillfind-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
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
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- Agenta-AI/agenta★ 4.9ksame name
- tddworks/ClaudeBar★ 1.6ksame name
- leonvanzyl/agentic-coding-starter-kit★ 447same name
- tddworks/asc-cli★ 393same name
- nockawa/Typhon★ 253same name
- tddworks/SkillsManager★ 165same name
- DGouron/review-flow★ 44same name
- kiminmonaco/ClaudeBar★ 8same name
- mgiovani/cc-arsenal★ 8same name
- leonvanzyl/claude-code-pro-workflow-demo★ 4same name
17 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
- CLAUDE.mdCLAUDE.md
- close-stageSkill
- commit-progressSkill
- debug-liveSkill
- evaluate-modelSkill
- exploreSkill
- run-testsSkill
- run-testsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
4
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
- Distinctive: line 12
One feature at a time: If something else is in flight, stop (rule 2).
- Very specific: line 20
Add a FakeModel test in tests/ (see tests/README.md) — the loop's contract, zero tokens.
- Very specific: line 26
If the change touches the full stack, run the exit gate: uv run python acceptance/run.py <provider> (see acceptance/README.md).
- Distinctive: line 30
Update the folder's
README.md: if you added, removed, or renamed a file — the README is that folder's live map, and this step is how the … - Distinctive: line 31
Update the status line in the root CLAUDE.md if a stage milestone completed.
- Distinctive: line 32
Ask the owner: when a decision changes scope or direction (rule 7).
“Common” is measured: kept by at least 6 in 10 of the 25 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 a feature (the constitution's mini-cycle)
The working rules in the root CLAUDE.md are law. This skill is those rules, as steps.
Before code
- One feature at a time. If something else is in flight, stop (rule 2).
- Study 2–3 seniors — mini-swe-agent, opencode, aider, Claude Code — for how they do this thing. Copy first, invent later; custom ideas wait for Stage 3 (rule 1).
- Write the design note
docs/notes/NN-name.md(next number): one page — what the seniors do → what we'll build → how we'll know it works. No note, no code (rule 6).
Code
- Implement under
src/harness/. Match the surrounding style and comment density. No line you can't explain (rule 3). - Respect the invariants in
src/harness/CLAUDE.md: the loop stays pure/injected; adapters translate both directions; tools return strings; errors become text, never crashes. - Add a FakeModel test in
tests/(seetests/README.md) — the loop's contract, zero tokens.
Prove it
uv run pytest -q— must stay green (rule 5).- Debug loop logic on ollama (a runaway loop costs $0); validate quality on gemini. Never point a possibly-buggy loop at a paid endpoint (the budget rule).
- If the change touches the full stack, run the exit gate:
uv run python acceptance/run.py <provider>(seeacceptance/README.md).
Finish
- Update the folder's
README.mdif you added, removed, or renamed a file — the README is that folder's live map, and this step is how the hierarchy stays un-rotten (note 15). - Update the status line in the root
CLAUDE.mdif a stage milestone completed. - Ask the owner when a decision changes scope or direction (rule 7).
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.

