releaselisted

# /requivo:release Write **release notes** — client-facing, for a non-technical stakeholder to understand what they're getting and why it matters. Not a changelog, not a spec. **You** write it; Requivo tracks the document. This mirrors `src/requivo/assets/prompts/release.md` and the `ReleaseNotes` contract in `core/contracts.py`, at commit `969cfd9` — the same rules the CLI's `requivo release` gives its own reasoning call, restated here because the plugin cannot import that file at runtime (`decision: plugin-skills-mirror-a-pinned-cli-commit`). Read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` unless you already hold it from an earlier `/requivo:*` in this conversation — and read it again whenever you are unsure you still do. ## 0. Preflight Run the shared **preflight** from REASONING.md before anything else: `requivo doctor --json`, checking whether the command ran *at all* rather than what it reported. If it could not run, the `requivo` CLI is not installed — follow REASONING.md's missing-CLI flow. Nothing has been saved at this point, so there is no half-written release note to find. ## 1. Load the model ``` requivo model show <slug> requivo status <slug> --json ``` Note the `revision` — call it `N`. It is the model these notes will rest on, and you will state it when you save. ## 2. Reason → write the notes - `title`: the feature name as a user would recognise it. Leave `version` for the caller to add later unless the model states one. - `summary`: 2–3 sentences, plain lang