devtools-stack-templatelisted

# devtools-stack-template Return the template payload for the slug the caller names, per the stack-adapter contract. The valid slugs are **exactly** the ones `/devtools:devtools-stack-menu` lists, and nothing else. > **`invocation` must stay `both`** — see `devtools-stack-menu`. An unknown slug is an **error**, not a guess. Name the slugs that do exist, and add that a managed container host comes from the project's cloud plugin rather than from here. Never answer a slug this plugin has not written from general container knowledge — a template it has not written is a template it does not offer. ## How to answer 1. Read `${CLAUDE_PLUGIN_ROOT}/stacks/<axis>/<slug>.md` — the template file, whose own `axis:` frontmatter key is authoritative for the axis. 2. Return **only** the payload below, filled from it. No prose around it, no summary of what you read, no advice. ```yaml slug: <the requested slug> axis: <the file's own axis: key> capabilities: [] # backing only — capability-vocabulary tokens it realizes artifact: <token> # deploy only harness: # how THIS stack satisfies each vwf capability <capability>: { task: <name>, mechanism: <one line> } # or n/a conventions: | <the template's prose — the artifact, the release path, configuration and secrets, the private plane, health, the decisions plan and execute need. Verbatim from the file; do not summarize it away.> ``` ## What belongs in `conventions`, and what does not The payload carries **judgment**, not API