What problem does it solve? Turning a chosen tech stack into an actual scaffolded codebase is error-prone: starter CLIs can clobber existing files, starters go stale, and fresh dependency trees ship with unknown vulnerabilities. This Skill automates the scaffold step with a strict conflict policy and a written verification trail. ## Core Features & Use Cases - Hand-off-driven scaffolding: Reads context/foundation/tech-stack.md written by the tech-stack selector, resolves the starter by starter_id against the starter registry, and runs its CLI with the correct cwd strategy (temp-dir move-up, native cwd, or git clone). - Strict conflict policy: Existing files are never overwritten — context/ is always preserved, .gitignore is append-merged, and clashes become .scaffold sibling files for manual diffing. - Pre- and post-scaffold verification: Checks starter recency via npm and GitHub before scaffolding, then runs the ecosystem's audit tool (npm audit, pip-audit, cargo audit, govulncheck, etc.) and writes a full verification log to context/changes/bootstrap-verification/verification.md. - Use Case: After running the tech-stack selector for a Next.js project, invoke this Skill to scaffold the app into the current directory, get warned if the starter is stale, see a severity-tiered audit of the fresh dependency tree, and receive a complete audit-trail log. ## Quick Start Bootstrap the project using the tech-stack hand-off at context/foundation/tech-stack.md and scaffold the app into the current directory.
