Run once per project to prepare it for the SDD pipeline. Copies the scaffold into project/work-items/, checks AGENTS.md for the build and test commands and asks for them when missing, and reports which optional inputs the other skills will find.
Prepare the current project for the sdd: skills. Explore first, then present what you found, then write only what the user confirms. Run it again at any time: it never overwrites a file that already exists.
1. Explore
Section titled “1. Explore”Look, and change nothing yet.
The scaffold source. The scaffold ships inside this skill, in the scaffold/ directory next to this SKILL.md, so it matches the installed version of the skills. If that directory is missing, stop and tell the user to reinstall the skills.
The scaffold target. List which files under the scaffold’s project/work-items/ already exist in the project root, and which are missing.
AGENTS.md. Check whether AGENTS.md exists at the project root. If it does, look for the command that builds the project and the command that runs its tests. A command counts as present only when it is written out, for example ./gradlew build or npm test.
Optional inputs. Check for each of these:
| Input | Where to look | Read by |
|---|---|---|
| OpenAPI | **/openapi.yaml, docs/apis/**/*.yaml |
discovery, spec generator, design review, implementation audit |
| Architecture | **/ARCHITECTURE.md, project/architecture/**, docs/architecture/** |
discovery, spec generator, design review, implementation audit |
| Domain terms | **/UBIQUITOUS_LANGUAGE.md |
discovery, spec generator, design review |
2. Present
Section titled “2. Present”Report the findings in three short sections, one at a time, and lead each with what you recommend.
- Scaffold. The files you will copy, and the files you will leave alone because they exist. Recommend copying every missing file.
- AGENTS.md. If both commands are present, quote them and move on. If
AGENTS.mdis missing, or either command is missing, ask the user for the missing command. Ask one question at a time. Also ask for a type-generation command, and accept “none”. - Optional inputs. For each input, the path you found, or “not found”. A missing input is not an error: the skills record it as a note in the spec. Do not offer to create these files.
3. Confirm
Section titled “3. Confirm”Show the exact text you will add to AGENTS.md, and the list of files you will copy. Wait for the user’s approval.
4. Write
Section titled “4. Write”- Copy each missing scaffold file into the project root, keeping its path under
project/work-items/. Never overwrite an existing file. - Add the commands to
AGENTS.mdunder a## Build and testheading. CreateAGENTS.mdif it does not exist. If the heading exists, add the missing lines under it rather than adding a second heading.
5. Done
Section titled “5. Done”Tell the user:
- What you copied and what you left alone.
- That the next step for a feature is
/sdd:spec-discovery, and for a bug report/sdd:spec-generator. - That
/sdd:spec-workflowdescribes the whole pipeline, and that implementation and branch close-out need the superpowers plugin or an equivalent.
The story behind this skill
Section titled “The story behind this skill”No post yet.
See it in the worked example
Section titled “See it in the worked example”Spec 38 was written before this skill existed.
The worked example walks through every artefact.