sdd-eng
Skill1 starsChanged 51 days agoNo licenceView on GitHub
Implements a behavior change in a product that already has (or is getting) an SDD map: edit the owning durable file and the code it points at, load only what this turn needs, and do not mint a per-feature spec/plan/tasks tree. Use when the user is coding a feature, fix, or refactor against an existing README, architecture, design, eval, or ADR, including when that file is on disk and not yet a map bullet, and including empty-shelf / empty-copy UI copy against a living docs/design.md. Do not use when creating or omitting product docs, distilling a PRD or idea dump, promoting scratch or a Proposed line, scaffolding Spec Kit / OpenSpec / Kiro, dual-writing CLAUDE.md, writing a markdown twin of OpenAPI or schema, or deciding whether a new durable file should exist. Do not use for a one-line edit, rename, or format pass. Do not use when the user attached another pack's skill this turn.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/blast-radius.mdcCursor rule
- .cursor/rules/comments-belong-in-docs.mdcCursor rule
- .cursor/rules/reply-shape.mdcCursor rule
- .cursor/rules/tdd.mdcCursor rule
- .cursor/rules/unfurnished-bias.mdcCursor rule
- .cursor/rules/yagni-bias.mdcCursor rule
- .cursor/rules/yagni.mdcCursor rule
- blueprintSkill
- evalsSkill
- grillSkill
- sddSkill
- ticketSkill
- unfurnishedSkill
- verifySkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.