Scaffold a Project

Bootstrap a greenfield repository to a verified baseline: a skeleton where every quality tool is wired and demonstrably working, so the first feature starts from green.

Do not skip ahead to feature code. The deliverable is the harness, proven by one passing example test — nothing more.

Track progress

Create a todo for each step below (0–4) and complete them in order, checking each off only when its Done when is met. Step 0 is a gate: if it stops you (not greenfield), abandon the list and redirect. Otherwise the failure this guards against is a skipped step — the baseline never verified, or the configure-repo hand-off forgotten.

0. Confirm the target is greenfield — GATE

Scaffolding writes a project root (git repo, root manifest, root README, root CI, root pre-commit hook). Doing that on top of an existing project collides with or overwrites real config. So before anything else, resolve where you are scaffolding and prove it is empty. This gate is not optional and it is not a judgment call you make by feel — run the check.

Resolve the target directory. Default to the current working directory. If the user named a destination ("scaffold a bot package under packages/"), the target is that path. If the cwd is itself a populated repo root but the user asked for a new subpackage, resolve the target to that new subdirectory and classify that — do not stop at the root's verdict.

Inspect it yourself (never ask the user what is in the directory — look):