spec-implement
Skill9 starsChanged 4 months agoMITView on GitHub
Implement a proposed spec. Reads the spec folder, follows the task checklist, writes code using TDD. Use after spec-propose is complete and approved.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- benjaminthomas/spec-driven-devtheir own version, first seen Nov 8, 2026
- stjarnstrom/spec-systemtheir own version, first seen Oct 15, 2026
- anyoneanderson/agent-skillstheir own version, first seen Oct 13, 2026
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- martinffx/ateliertheir own version, first seen Oct 9, 2026
- h3y6e/spec-skillstheir own version, first seen Feb 23, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- martinffx/atelier★ 51same name
- xfstudio/skills★ 9same name
- anyoneanderson/agent-skills★ 3same name
- benjaminthomas/spec-driven-dev★ 2same name
- h3y6e/spec-skills★ 0same name
- stjarnstrom/spec-system★ 0same 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 repository8 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- auth-implementationSkill
- incident-responseSkill
- kiro-railsSkill
- review-guideSkill
- spec-archiveSkill
- spec-proposeSkill
- spec-verifySkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
8
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
- Distinctive: line 13
Confirm readiness: - all artifacts exist and tasks are defined
- Distinctive: line 19
Update design.md: if implementation deviates from plan (document WHY)
- Distinctive: line 23
Before writing any code, verify:
- Very specific: line 34
Mark progress: - update - [ ] to - [x] in tasks.md after each task passes tests
- Distinctive: line 35
Stay in scope: - if you discover needed work not in the spec, note it but don't implement it.
- Distinctive: line 37
Document deviations: - if the implementation differs from design.md, update design.md with the actual approach and rationale
- Distinctive: line 41
When all tasks are checked off:
- Distinctive: line 42
Run the full test suite
- Distinctive: line 43
Verify all acceptance criteria in requirements.md are met
“Common” is measured: kept by at least 6 in 10 of the 6 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
Spec Implement Workflow
Implement a feature that has an approved spec in .kiro/specs/<feature-name>/.
Steps
- Read the full spec - proposal.md, requirements.md, design.md, tasks.md
- Confirm readiness - all artifacts exist and tasks are defined
- Implement using TDD - for each task:
- RED: Write a failing test
- GREEN: Write minimal code to pass
- REFACTOR: Clean up while tests pass
- Check off tasks as completed in tasks.md
- Update design.md if implementation deviates from plan (document WHY)
Pre-Implementation Checklist
Before writing any code, verify:
proposal.mdexists and is approved (user confirmed)requirements.mdhas testable acceptance criteriadesign.mddescribes the approachtasks.mdhas atomic, ordered tasks- No open questions remain in proposal.md (or they've been answered)
Implementation Rules
- Follow task order - implement tasks in the sequence defined in tasks.md
- One task at a time - complete and verify each task before starting the next
- Mark progress - update
- [ ]to- [x]in tasks.md after each task passes tests - Stay in scope - if you discover needed work not in the spec, note it but don't implement it. Add it as a new task or flag it for a follow-up spec.
- Test against acceptance criteria - each requirement's criteria must have a corresponding test
- Document deviations - if the implementation differs from design.md, update design.md with the actual approach and rationale
Completion
When all tasks are checked off:
- Run the full test suite
- Verify all acceptance criteria in requirements.md are met
- Inform the user the spec is ready for verification (use
spec-verify)
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.

