What problem does it solve? Requirements are often developed ad-hoc with no version control, no status tracking, and no way to answer "how many requirements are done?" This Skill sets up the ongoing management infrastructure that keeps requirements organized, tracked, and controlled after they are initially developed. ## Core Features & Use Cases - Infrastructure Setup: Select a requirements management tool by project size, define an attribute schema, choose an ID labeling convention, and map status workflow transitions to roles. - Baselining & Change Control: Freeze validated requirements as version 1.0, define change control thresholds, and route modifications through a CCB with impact analysis. - Status Monitoring & Reporting: Track requirements through a nine-state lifecycle (Proposed to Verified), maintain burndown charts, and produce per-sprint status reports. - Use Case: A team with 200 requirements and no tracking uses this Skill to define a 12-attribute schema in a spreadsheet, establish a status workflow, and generate sprint burndown reports that surface a testing bottleneck. ## Quick Start Set up a requirements management process for my project, including an attribute schema, ID labeling convention, status workflow, and a sprint status report template.
