cookiecutter-template-managelisted

# Cookiecutter Template Manage Orchestrates the full Cookiecutter template lifecycle. The skill owns all mid-flow user confirmations — variable names, choice defaults, hook additions that affect generated output — then dispatches the `cookiecutter-template-author` agent for the pure authoring step once every decision is locked in. The agent never asks for approvals; that dialogue belongs here. ## Why this is a skill, not an agent - **Mid-flow confirmations are the load-bearing interaction** — variable-name proposals, choice-default selections, and one-way hook additions all require explicit user sign-off before any file is written. An agent's fire-and-forget contract forfeits those checkpoints; a skill's conversational turn model owns them. - **Orchestrator role** — per `spec/claude/skill-vs-agent/<canonical_language>.md` §Hybrid pattern, when a workflow's orchestration requires user dialogue but the execution step benefits from a narrow specialist, the orchestrator is a skill and the executor is an agent. This skill is the orchestrator; `cookiecutter-template-author` is the executor. - **Output flows back into the main conversation** — confirmation of variable names, the pre-dispatch decision summary, and the post-agent follow-up checklist are all part of the user's working context and must not be buried in a structured agent report. - Counter-dimension considered: the authoring step itself (reading every template file, running `cookiecutter --no-input`, executing `pytest