ddd-ground
Skill44 starsChanged 7 days agoMITView on GitHub
Produce a documentation-grounded plan with cited decisions and useful snippets, save its research, or continue an authorized implementation.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Keep proposed application explanations visibly proposed until implementation and checks establish them.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Ground the plan and implementation
Load the ddd skill completely, through your native skill tool when you have one, otherwise by reading
DDD, and apply Keep one persistent note and ground the
plan, performing steps 1 and 2 first wherever questions or sources are missing.
That skill owns the procedure and Documentation basis format.
Finish a planning request with a saved plan: cited decisions, useful snippets labeled by origin and execution status, checks to run, and open questions. Stop before implementation when only a plan was requested.
For authorized implementation, continue through DDD's steps 4 and 5. Consult new APIs and research failed assumptions before workarounds; maintain the same note and compare actual code against sources. No claims or trace ledgers are required.
Keep proposed application explanations visibly proposed until implementation and checks establish them. Use snippets only for consequential choices.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- guide/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- ddd-scopeSkill
- dddSkill
- ddd-verifySkill
- diagnosing-bugsSkill
- domain-modelingSkill
- engineering-workflowSkill
- frontend-designSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- herdrSkill
- implementSkill
- implement-specSkill
- improve-codebase-architectureSkill
- prototypeSkill
- prSkill
- receiving-code-reviewSkill
- researchSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- tddSkill
- teachSkill
- team-leadSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- verification-before-completionSkill
- wait-whatSkill
- wayfinderSkill
- wizardSkill
- writing-for-agentsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

