stackgen-stack-templatelisted

# stackgen-stack-template Return the template payload for the slug the caller names, per the vwf stack-adapter contract. This skill is the **dispatch rule**, and dispatch runs **per component**: materialized entries are read back; a first pin resolves the bundle's composition and materializes each component — shipped packs by copy, uncovered components by generation. Materialization is **explicit and consent-gated — never a silent re-run**. > **`disable-model-invocation` must stay `false`** — see > `stackgen-stack-menu`. ## Resolution order 1. **Materialized already?** Read `.claude/stackgen/templates/<slug>.md` at the repo root (in a worktree, the tree is part of the checkout like any committed file). If it exists: return the payload below, filled from its frontmatter with the body as `conventions:`. **Stop — never regenerate, never diff.** Drift against packs is `/stackgen:stackgen-sync`'s job, on the user's clock — and it acts per component. 2. **A first pin? Resolve the composition.** The slug names the bundle root — a shipped pack (`${CLAUDE_PLUGIN_ROOT}/stacks/<type>/<slug>/pack.yaml` exists), or `generated/<technology-slug>` when the root itself is uncovered. Resolve the rest of the composition per the root's kind and the component types that compose it (`${CLAUDE_PLUGIN_ROOT}/assets/kinds.md`, `${CLAUDE_PLUGIN_ROOT}/assets/taxonomy.md`): read the repo's manifests and the config's `stack` block (`languages` / `frameworks` / `d