What problem does it solve? Once a requirements baseline is approved, uncontrolled changes cause scope creep, stale specifications, and untraceable implementations. This Skill governs the post-baseline lifecycle: processing change requests through a Change Control Board, maintaining forward and backward traceability, and versioning the requirements baseline. ## Core Features & Use Cases - CCB Change Request Pipeline: Register CRs, run impact analysis across specification, design, code, and tests, and route decisions through a formal Change Control Board with defined quorum rules. - Traceability Matrix Management: Maintain forward (Req → Design → Code → Test) and backward traceability with coverage metrics and health signals via the count-requirements.sh script. - Baseline Versioning & Change Log: Apply semantic versioning rules to the specification (v1.0.1 fixes, v1.1 new requirements, v2.0 scope shifts) and document every change in a structured change log. - Use Case: A stakeholder requests a new reporting requirement mid-sprint. Use this Skill to log the CR, assess impact on 12 existing requirements, present it to the CCB, and update the traceability matrix and baseline version upon approval. ## Quick Start Ask the assistant to run the rm-management step to register a new change request and update the requirements traceability matrix for the current work package.
