claude-code-stack-menulisted

# claude-code-stack-menu Return the templates the `claude-code` 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 an authoring plugin is on the stack menu at all `claude-code` is doctrine for extending Claude Code, and most of what it owns is exactly that. It carries **one** template, on the **project** axis: a project whose registry `platforms:` is `[ plugin ]` — a Claude Code plugin, which is a directory of markdown and a manifest rather than a program. That template is what makes the `plugin` platform buildable. vwf covers `plugin` projects in the blueprint as of blueprint format 23, and a covered project needs a pin its `doctor` run can check against; without one, the project's language token resolves to `unknown`, which is **blocking**. ## 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: claude-code note: This plug