Requirement Review

---
name: requirement-review
description: Independently assess proposed IR/SR changes or a justified reuse conclusion, with their supporting Feature and Scenario analysis. Establish the first requirement basis for downstream design.
---

# Requirement Review

Review the request interpretation and proposed requirement basis together. Assess fidelity to the RR, existing ownership and duplication, stakeholder scope, assessability, material uncertainty and relevant Feature/Scenario coverage. A justified no-change conclusion can pass without manufacturing requirement edits.

The author does not provide independent approval of their own subjects. Record actual reviewer/contributor attribution, inspected subjects, governing basis, findings and limitations. Approval permits downstream design to rely on the reviewed obligations; it does not establish Function completeness, allocated ARs, implementation correctness or permission for external actions.

Do not require complete Function or AR allocation as a condition of approving requirements for design. Return wrong needs, missing obligations and scope conflicts to requirement-analysis. Review corrections against their effects while maintaining adequate coverage of the complete current requirement basis. Earlier approval never silently covers rewritten obligations.

Use review prepare/show/record for the requirements purpose. The requirement owner can select the resulting accepted Basis after applicable approval is recorded. Retain unresolved findings through later submissions; a save creates no approval beyond the reviewer's actual conclusion.

## Recording boundary

For Change-managed work, read the packaged operational interface reference before relying on or updating current state. Use supported CLI tasks and the inspected opaque revision; skills do not use SQL or edit runtime storage. An isolated invocation keeps its requested scope. Installation alone does not adopt workflow policy.

## Resource map

- READ `references/operational-recording.md` when inspecting or recording Change-managed work.
- READ `references/targeted-recording-v2.schema.json` when constructing a recording request.
- READ `references/rigorloop-records-v4.schema.json` when checking the types used by that request.

- READ `references/rem-models-requirements.md` when assessing requirement validity and acceptance.
- READ `references/rem-models-scenarios.md` when assessing affected Scenario coverage.
- READ `references/rem-models-system-design.md` when assessing Feature meaning.
- READ `references/rem-methods-requirement-analysis.md` when checking analysis sufficiency or reuse.

- READ `references/requirement-to-delivery-model.md` when applying its criteria to this responsibility.

- READ `references/review-reliance.md` when applying its criteria to this responsibility.

- READ `references/review-assessment.md` when applying its criteria to this responsibility.

## Expected output

Report the actual scoped outcome, governing basis, changed subjects or recorded judgment, material gaps and the next authorized action. Distinguish progress, review approval, final verification and external publication; claim only outcomes supported by this invocation.