criterialisted

# /requivo:criteria Write **acceptance criteria** — a test-ready specification a QA engineer can run against the built feature and a client can sign off on. **You** write it; Requivo tracks the document. This mirrors `src/requivo/assets/prompts/criteria.md` and the `AcceptanceCriteria` contract in `core/contracts.py`, at commit `969cfd9` — the same rules the CLI's `requivo criteria` 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 checklist 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 criteria will rest on, and you will state it when you save. ## 2. Reason → write the checklist - Write scenarios in **Given / When / Then** form: `given` is the starting state, `when` is the single triggering action, `then` is the observable outcomes to check — either ca