prdlisted

# /requivo:prd Generate a **PRD as a view of the model** — not new invention. **You** write it from the model; Requivo tracks it. Read `${CLAUDE_PLUGIN_ROOT}/REASONING.md` first. ## 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 — say the four things REASONING.md lists and stop. Nothing has been saved at this point, so there is no half-written PRD to find. ## 1. Load the model ``` requivo model show <slug> requivo status <slug> --json ``` Note the `revision` — call it `N`. It is the model this PRD will rest on, and you will state it when you save. ## 2. Reason → write the PRD Turn the model into a PRD (title, summary, problem, goals, users, in/out of scope, requirements with priorities, workflow, business rules, permissions, integrations, edge cases, acceptance criteria, assumptions, open questions, risks). Rules that keep it faithful to the model: - **Unknowns stay visible.** A slot that is empty or `inferred` becomes an explicit *assumption* or an *open question* in the PRD — never a stated requirement. - **Open decisions stay open.** Do not silently resolve a decision the model left open. - **Traceability.** Each requirement should be traceable to the slot(s) it comes from; keep them grounded in the model, not added from outside it. ## 3. Save it as a tracked artifact Pass the P