What problem does it solve? Change requests often get approved or rejected based on gut feeling, leading to hidden costs, scope creep, and out-of-sync artifacts. This Skill provides a structured three-step impact analysis so every change decision is informed by real cost, schedule, and risk data. ## Core Features & Use Cases - Three-Step Impact Analysis: Systematically evaluate implications, identify all affected work products (SRS, architecture, tests, docs, training), and estimate effort, schedule, and cost. - 18-Field Change Request Record: Capture every standard attribute from Wiegers, from requester and rationale through CCB resolution, for full traceability and audit readiness. - Use Case: A lab director requests barcode scanning mid-release. Use this Skill to trace ripple effects across requirements, architecture, and test plans, estimate 90 hours of effort plus hardware cost, compare alternatives including "do nothing", and deliver a defer-to-Release-2 recommendation to the change control board. ## Quick Start Analyze the impact of change request CR-007 for adding barcode scanning and prepare a recommendation for the change control board.
