What problem does it solve? Adopting a documentation template requires manually replacing dozens of placeholders, pruning irrelevant docs, and configuring permissions — a slow, error-prone process. This Skill automates that instantiation through a guided interview, detecting whether the project is new or existing and adapting the template accordingly. ## Core Features & Use Cases - Context Detection: Inspects the repository (code files, git history, remaining placeholders) to deduce whether the project is new or existing before asking questions. - Guided Interview: Asks only what cannot be inferred — identity, stack, capabilities, and permission policy — pre-filling answers from the codebase in existing projects. - Placeholder Filling & Cleanup: Replaces the full placeholder catalog across README, docs, LICENSE, and .env.example, then deletes conventions and skills that do not apply to the project type. - Use Case: You clone a project starter template and run the instantiation flow; the Skill fills in your project name, stack, and commands, removes SEO docs for an API-only project, writes a .template-origin file, and records the setup as an ADR. ## Quick Start Ask the assistant to instantiate this template for your project and answer the guided interview questions about your stack and project type.
