Scaffold Project

Generate a new project skeleton on disk. The skeleton is empty but fully wired: every package compiles, the DI container boots, and / serves hello-world. From there the user hands off to domain-specific skills.

Workflow overview

1. Interview — ask the user in batches (see references/interview.md).
2. Confirm — show the resolved config + file tree, ask "proceed or revise".
3. Generate — for each selected layer, read .tmpl files from assets/, substitute placeholders, write with the Write tool.
4. Print checklist — next-step commands and which specialized skill to invoke next.

Guardrails

Read these before writing anything:

• Never invent template content. Every file comes from assets/. If a template does not exist for a requested combination, emit a TODO(scaffold): comment in the generated file and move on.
• Do not run pnpm install. The user does this themselves.
• Do not run git commit, start servers, or trigger CI. The skeleton ships un-committed so the user can inspect it.
• Do not create domain content — no entities, use cases, repo implementations, DTOs, value objects. The entity, usecase, persistence, etc. skills own those surfaces.