spec-driven-implementation
Skill2.1k starsChanged 6 months agoAGPL-3.0View on GitHub
Drive a spec-first workflow for substantial features by writing PRODUCT.md before implementation, writing TECH.md when warranted, and keeping both specs updated as implementation evolves. Use when starting a significant feature, planning agent-driven implementation, or when the user wants product and tech specs checked into source control.
5 other projects use a version of this, 3 of them edited.
Trending
Quiet since September.thin dataabout the whole repository
Most recently taken up by
- warpdotdev/common-skillsedited, first seen Oct 20, 2026
- zhouycheng/skillsedited, first seen Oct 13, 2026
- zerx-lab/warpword for word, first seen Oct 8, 2026
- robisson/build-like-amazon-agent-skillstheir own version, first seen Oct 5, 2026
- thesammykins/skillsedited, first seen Aug 14, 2026
Who's talking about zerx-lab/zap
- @personhood.removal.surgery“they went open source and let you BYOK now, it FUCKS, and there's community forks. i also had no interest …”Bluesky · Jun 26, 2026 · 8 likes
- byte5ai/zaplex“feat(terminal): complete Kitty graphics protocol”GitHub · Sep 8, 2026
- byte5ai/zaplex“feat(byop): Ollama-Tool-Calls aus strukturiertem Assistant-Text übernehmen”GitHub · Sep 6, 2026
- byte5ai/zaplex“fix(byop): Provider-Routing für OpenAI, Anthropic und Ollama härten”GitHub · Sep 6, 2026
- byte5ai/zaplex“feat(terminal): Kitty Graphics Protocol vervollständigen”GitHub · Sep 6, 2026
The biggest 5 of 8 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 8
Talked about on GitHub and Bluesky (8 times).
On GitHub · 7
- Sep 8, 2026feat(terminal): complete Kitty graphics protocol — byte5ai/zaplex0 reactions
- Sep 6, 2026feat(byop): Ollama-Tool-Calls aus strukturiertem Assistant-Text übernehmen — byte5ai/zaplex0 reactions
- Sep 6, 2026fix(byop): Provider-Routing für OpenAI, Anthropic und Ollama härten — byte5ai/zaplex0 reactions
- Sep 6, 2026feat(terminal): Kitty Graphics Protocol vervollständigen — byte5ai/zaplex0 reactions
- Sep 6, 2026fix(agent): Mehrzeilige Pager-Wrapper heredoc-sicher schließen — byte5ai/zaplex0 reactions
2 more on GitHub
- Sep 6, 2026fix(ui): Kleine Zap-UI-Stabilitätsfixes selektiv portieren — byte5ai/zaplex0 reactions
- Jul 20, 2026增加Agent支持 — chi11321/CrabPort0 reactions · 3 comments
On Bluesky · 1
- Jun 26, 2026they went open source and let you BYOK now, it FUCKS, and there's community forks. i also had no interest in it when it was still a… — @personhood.removal.surgery8 likes and reposts · 1 reply
Other versions5 projects use a version of this.
Word for word · 1
- zerx-lab/warp★ 2.1k100% same
Edited · 3
- warpdotdev/common-skills★ 63094% same
- zhouycheng/skills★ 194% same
- thesammykins/skills★ 080% same
Wrote their own version · 1
- robisson/build-like-amazon-agent-skills★ 16same name
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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-feature-flagSkill
- add-telemetrySkill
- dedupe-issue-localSkill
- diagnose-ci-failuresSkill
- fix-errorsSkill
- implement-specsSkill
- promote-featureSkill
- remove-feature-flagSkill
- resolve-merge-conflictsSkill
- review-pr-localSkill
- review-prSkill
- rust-unit-testsSkill
- triage-issue-localSkill
- update-skillSkill
- warp-integration-testSkill
- warp-ui-guidelinesSkill
- write-product-specSkill
- write-tech-specSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 8 are common, 2 are distinctive, and 6 are very specific to this project.
8
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 4 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.
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.