sdd-onboarding-kit
AGENTS.md19 starsChanged 37 days agoMITView on GitHub
This repository is an SDD onboarding kit. It is not the target project configuration. These instructions apply to any coding agent (Claude Code, Codex, Cursor, OpenCode, Antigravity or another harness) opened in this repository. When the developer asks to install or configure SDD in another repository: The final goal is to create a project-specific SDD harness, not to explain SDD abstractly. When the developer asks to make changes in this repository:
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- broSkill
- closingSkill
- context-auditSkill
- decision-logSkill
- dependency-freshnessSkill
- documentation-updateSkill
- failure-learningSkill
- git-disciplineSkill
- goblin-modeSkill
- project-mapSkill
- run-and-verifySkill
- spec-from-screenshotSkill
- ui-qaSkill
- sdd-updateSkill
- sdd-workflowSkill
The file
We split this AGENTS.md into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
When the developer asks to install or configure SDD in another repository:
- Very specific: line 7
Start by reading instructions.md.
- Very specific: line 10
Use the files under templates/, agents/, skills/, hooks/, mcps/, and scripts/ as source material.
- Distinctive: line 11
Do not treat this kit's root AGENTS.md/CLAUDE.md as the final project instruction file.
- Distinctive: line 14
Ask the developer before enabling hooks, configuring MCPs, changing git policy, or assuming test/lint commands.
- Distinctive: line 18
When the developer asks to make changes in this repository:
- Very specific: line 20
If todolist.md exists (it is gitignored and local-only), read it: it contains the tasks to be done.
- Very specific: line 22
If bugs.md exists (also gitignored and local-only), check that the bugs it describes are solved.
- Very specific: line 24
After adding, renaming or deleting kit files, run scripts/update-manifest.sh to regenerate manifest.md.
- Distinctive: line 25
Keep every installable file harness-neutral: no harness name or harness-specific command in agents, skills, templates or policies unless it …
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Instructions for coding agents working inside this kit
This repository is an SDD onboarding kit. It is not the target project configuration. These instructions apply to any coding agent (Claude Code, Codex, Cursor, OpenCode, Antigravity or another harness) opened in this repository.
When the developer asks to install or configure SDD in another repository:
- Start by reading
instructions.md. - Then read
questions.md. - Then read
output-project-structure.md. - Use the files under
templates/,agents/,skills/,hooks/,mcps/, andscripts/as source material. - Do not treat this kit's root
AGENTS.md/CLAUDE.mdas the final project instruction file. - Generate or update the target project's own
AGENTS.mdfromtemplates/AGENTS.md.template(plus theCLAUDE.mdimport stub fromtemplates/CLAUDE.md.templatewhen Claude Code is one of the harnesses). - Map the kit's reference layout (
.claude/) to the harness being installed usingreference/harness-primitives.md. - Ask the developer before enabling hooks, configuring MCPs, changing git policy, or assuming test/lint commands.
The final goal is to create a project-specific SDD harness, not to explain SDD abstractly.
When the developer asks to make changes in this repository:
- If
todolist.mdexists (it is gitignored and local-only), read it: it contains the tasks to be done. If it does not exist, ask the developer what to change. - Complete the tasks. You may need to modify some of the hooks, MCPs, templates, etc.
- If
bugs.mdexists (also gitignored and local-only), check that the bugs it describes are solved. - Mark with X all the checkboxes of the tasks/bugs you complete.
- After adding, renaming or deleting kit files, run
scripts/update-manifest.shto regeneratemanifest.md. - Keep every installable file harness-neutral: no harness name or harness-specific command in agents, skills, templates or policies unless it is inside a per-harness table or example.
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.