repo-scaffold
Turn an empty repository into the smallest working starting point the design calls for, so the
detailed design and implementation build on real, verifiable ground. Scaffolding is not the
feature: write no feature behaviour.
Inputs
Your instructions name the approved HLD (its Repositories section lists each repository, its
stack and purpose), the repositories to scaffold (already created and committed empty) and where
to write the scaffold report. Standalone? scaffold the repositories the user names and tell them
where the report is.
For each repository
- Layout — the stack's conventional structure and package manager, at current stable
versions pinned in the lock file the stack uses. Follow the installed stack skill for that
stack when there is one.
- Build, test and lint — one trivial passing test, a build that compiles or packages it, and
the stack's standard linter configured. Every command runs from the repository root without
network access beyond installing declared dependencies.
- README — what the repository is for (from the HLD), how to build, test and run it.
- CI — a pipeline in the repository's CI system (GitHub Actions by default) that runs the
same build, lint and test commands.
- Deployability — when the HLD's Infrastructure and operations section deploys this
repository, a container image definition; when it names an infrastructure platform, that
repository's starting definitions (an empty Terraform root module, a Helm chart) — using the
matching infrastructure pack when installed.
- Codebase map — at the path your instructions name (by default
docs/codebase-maps/<name>.md): the layout, entry points and conventions, so later steps read
the map instead of exploring.
- Commit the skeleton on the repository's default branch.
Report
Write the scaffold report your instructions name as
{"repos": {"<name>": {"stack": "<stack>", "commands": {"build": "...", "test": "...", "lint": "...", "security": "..."}}}}. build and test are required; the engine adds them to
the project configuration and runs them once to prove the skeleton works.
Safety
Touch only the repositories you were given. No feature code, no secrets, no real credentials or
cloud resources; infrastructure definitions are files only — never apply them.
Output contract
Return summary: one line naming each repository scaffolded and its stack.
1---2name: repo-scaffold3description: Create the starting skeleton of new repositories from an approved high-level design — project layout, a passing build and test, lint, a README, CI, a container image when the design deploys one, and a codebase map — and report each repository's commands. Front door for /repo-scaffold.4allowed-tools: Read, Grep, Glob, Bash, Edit, Write5tags: [sdlc, implement, greenfield]6metadata:7 source: https://skillmd.com/skills/keyvaluesoftwaresystems/repo-scaffold8---910# repo-scaffold1112Turn an empty repository into the smallest working starting point the design calls for, so the13detailed design and implementation build on real, verifiable ground. Scaffolding is not the14feature: write no feature behaviour.1516## Inputs1718Your instructions name the approved HLD (its Repositories section lists each repository, its19stack and purpose), the repositories to scaffold (already created and committed empty) and where20to write the scaffold report. Standalone? scaffold the repositories the user names and tell them21where the report is.2223## For each repository24251. **Layout** — the stack's conventional structure and package manager, at current stable26 versions pinned in the lock file the stack uses. Follow the installed stack skill for that27 stack when there is one.282. **Build, test and lint** — one trivial passing test, a build that compiles or packages it, and29 the stack's standard linter configured. Every command runs from the repository root without30 network access beyond installing declared dependencies.313. **README** — what the repository is for (from the HLD), how to build, test and run it.324. **CI** — a pipeline in the repository's CI system (GitHub Actions by default) that runs the33 same build, lint and test commands.345. **Deployability** — when the HLD's Infrastructure and operations section deploys this35 repository, a container image definition; when it names an infrastructure platform, that36 repository's starting definitions (an empty Terraform root module, a Helm chart) — using the37 matching infrastructure pack when installed.386. **Codebase map** — at the path your instructions name (by default39 `docs/codebase-maps/<name>.md`): the layout, entry points and conventions, so later steps read40 the map instead of exploring.417. **Commit** the skeleton on the repository's default branch.4243## Report4445Write the scaffold report your instructions name as46`{"repos": {"<name>": {"stack": "<stack>", "commands": {"build": "...", "test": "...",47"lint": "...", "security": "..."}}}}`. `build` and `test` are required; the engine adds them to48the project configuration and runs them once to prove the skeleton works.4950## Safety5152Touch only the repositories you were given. No feature code, no secrets, no real credentials or53cloud resources; infrastructure definitions are files only — never apply them.5455## Output contract5657Return `summary`: one line naming each repository scaffolded and its stack.