What problem does it solve? Turning a chosen tech stack into an actual scaffolded codebase is error-prone: starter CLIs differ in how they handle the working directory, existing files can be clobbered, and there is no record of what happened. This Skill reads the tech-stack hand-off written by the tech-stack selector, runs the correct starter CLI with a strict conflict policy, and logs verification findings so nothing is lost. ## Core Features & Use Cases - Registry-driven scaffolding: Looks up the chosen starter by starter_id in the tech-stack-selector registry and dispatches one of three cwd strategies (subdirectory-then-move, native-cwd, or git-clone) with a conflict matrix that always preserves context/ and never deletes user files. - Two verification slots: A pre-scaffold recency check (npm publish date, GitHub last-push) and a post-scaffold dependency audit (npm audit, pip-audit, cargo audit, etc.) with severity tiering, both warn-and-continue rather than blocking. - Audit trail: Writes a structured context/changes/bootstrap-verification/verification.md capturing the hand-off, scaffold log, audit findings, and hints recorded but not acted on. - Use Case: After running the tech-stack selector for a new Astro project, invoke this Skill to clone the starter, merge it into your directory without overwriting your planning docs, and get a dependency vulnerability summary on day one. ## Quick Start Ask the assistant to bootstrap the project using the hand-off at context/foundation/tech-stack.md after you have run the tech-stack selector.
