Requirement Analysis

---
name: requirement-analysis
description: Reconcile a request, proposal, issue or incident with existing IRs, SRs, Features and Scenarios. Propose justified reuse, refinement or new requirements before requirement review.
---

# Requirement Analysis

Treat incoming material as RR input. Preserve its source and meaning; a suggested technology or approved direction is not automatically an engineering obligation.

Inspect the applicable existing requirements before creating identities. Compare need, scope, conditions and acceptance: reuse without modification is a valid outcome; refine an existing requirement when its meaning evolves; create an IR only for a distinct durable need. One RR may affect several needs. Keep unresolved or conflicting portions visible.

Apply the packaged Requirement Analysis and 5W2H methods when deriving or refining IR/SR content. Confirm the stakeholder-visible Feature and black-box Scenarios. Preserve stable IDs and the distinction between a capability, its concrete use and a delivery milestone. Derive assessable SRs, including relevant quality, data, failure and compatibility obligations. Do not create a Function per SR or demand complete Function/AR allocation before requirement approval.

Update the owning repository definitions and concise applicable rationale. Record RR interpretation, reuse/refinement/creation dispositions, scope, acceptance and material uncertainty in the current handoff. A separate proposal dossier is not required. Prepare the exact proposed requirement basis for independent requirement-review; do not finalize architecture or approve your own work.

## 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-methods-requirement-analysis.md` when reconciling RR and deriving IR/SR obligations.
- READ `references/rem-methods-scenario-analysis.md` when analyzing stakeholder use.
- READ `references/rem-methods-5w2h.md` when creating or materially refining a requirement.
- READ `references/rem-models-requirements.md` when checking requirement identities and relationships.
- READ `references/rem-models-scenarios.md` when editing governed Scenarios.
- READ `references/rem-models-system-design.md` when confirming Feature meaning.

- READ `references/requirement-to-delivery-model.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.