sdd-change
Skill3 starsChanged 3 months agoApache-2.0View on GitHub
Use when implementing a meaningful repository change that requires an approved spec before code edits.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- mariano-aguero/spec-driven-development-skilltheir own version, first seen Nov 8, 2026
- ad1code/sdd-harnesstheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- mariano-aguero/spec-driven-development-skill★ 11same name
- ad1code/sdd-harness★ 4same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- final-reviewSkill
- grill-changeSkill
- implement-nextSkill
- request-to-spec-issuesSkill
- subagent-driven-changeSkill
- tdd-changeSkill
- final-reviewSkill
- grill-changeSkill
- implement-nextSkill
- request-to-spec-issuesSkill
- sdd-changeSkill
- subagent-driven-changeSkill
- tdd-changeSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
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
- Very specific: line 12
Read the relevant spec in docs/specs/.
- Distinctive: line 14
Do not implement behavior outside the approved spec.
- Distinctive: line 15
Add or update focused tests where practical before changing behavior.
- Distinctive: line 16
Run relevant tests and golden tests before final review.
- Distinctive: line 21
Do not upload source code.
- Distinctive: line 22
Do not read or print secrets.
- Distinctive: line 23
Ask before mutating files, running shell commands, installing dependencies, or using external network access.
- Distinctive: line 24
Keep production access denied.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Generated by Agent Profile Compiler. Do not edit by hand. -->SDD Change
Instructions
- Read the relevant spec in
docs/specs/. - Confirm the problem, goal, non-goals, contracts, security rules, acceptance criteria, tests, documentation updates, and final checklist.
- Do not implement behavior outside the approved spec.
- Add or update focused tests where practical before changing behavior.
- Run relevant tests and golden tests before final review.
- Report any missing spec, Draft spec, test gap, or contract risk before proceeding.
Safety
- Do not upload source code.
- Do not read or print secrets.
- Ask before mutating files, running shell commands, installing dependencies, or using external network access.
- Keep production access denied.
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.