brse-spec-verifylisted

# BrSE Spec Verify ## Overview Verify a requirement document against ISO/IEC/IEEE 29148:2018 9-criteria before it is forwarded to developers or transferred to a delivery surface. **Core principle:** A populated section is not an approved section. Read the body, not the headings. Without the original source, `Correct` cannot be evaluated — mark it Unverified, never assume. ## When To Use - After `brse-requirement-clarifier` has produced a structured requirement. - Before `brse-spec-transfer` pushes a document to a delivery surface. - When reviewing a sprint-planning document inherited from another BrSE. - When a developer pushes back that a spec is unclear and the BrSE wants an objective check. ## When NOT To Use - The clarifier has not run yet — verify needs a structured doc, not raw customer input. - The doc is being authored, not reviewed — write first, verify last. - The doc is for a one-off internal note that will never go to dev or customer — skip the gate. - The target is implementation code, not a requirement — code review is a different skill outside this plugin. ## Inputs The skill needs two things: 1. **Target document** — the requirement to verify (Markdown, paste-in text, or Outline/Plane document via MCP). 2. **Original source** — the customer-facing input the document was derived from (JP spec, email, chat thread, meeting note). Without the original, the `Correct` criterion cannot be evaluated; mark it as `Unverified` and proceed. ## Workflow 1. Iden