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 specification. ## Core Features & Use Cases - CCB Change Control: Register change requests, run impact analysis across specification, design, code, and tests, and route decisions through a Change Control Board with defined quorum rules. - Traceability Matrix Management: Maintain forward (Req → Design → Code → Test) and backward traceability, with a shell script that counts requirements by state and reports coverage metrics and health signals. - Baseline Versioning & CR Kanban: Apply versioning rules (v1.0.1 for fixes, v1.1 for new requirements, v2.0 for scope shifts) and visualize active CRs in a Kanban board. - Use Case: A stakeholder requests a new payment feature mid-sprint. Use this Skill to log CR-008, complete the impact assessment template, present it to the CCB, update the baseline to v1.2, and refresh the traceability matrix. ## Quick Start Use the rm-management skill to register a new change request, run its impact analysis, and update the traceability matrix in the current work package.
