devtools-stack-menulisted

# devtools-stack-menu Return the templates the `devtools` plugin offers, per the stack-adapter contract. **Return the payload and nothing else** — no prose, no recommendation, no comparison. Choosing is the user's job and presenting the choice is vwf's. > **`invocation` must stay `both`.** A `user` skill is removed from the model's > context entirely and cannot be invoked programmatically — vwf does not get an > error, it gets an empty menu. ## Why a tooling plugin is on the stack menu at all `devtools` is the developer toolchain, and almost everything it owns is doctrine rather than a stack choice. It carries **one** template: the provider-neutral **deploy** option — build an OCI image, run it on any host that runs containers. That is the answer when the product must not be tied to one cloud, and it belongs here because Docker is developer tooling and the template names no provider. There is deliberately **no `container` capability plugin**: a container is not a backing capability, it is how a deployable is packaged. ## How to answer 1. List `${CLAUDE_PLUGIN_ROOT}/stacks/*/*.md`. Each file is one template: its **slug** is the filename without `.md`, its **axis** is that file's `axis:` frontmatter key, and its `name` + summary line come from the same frontmatter and the file's opening prose. 2. Return the payload below — `note` included, on every answer. ```yaml plugin: devtools note: This plugin offers the deploy axis only, and only its provider-neutral op