ba-requirements-lifecycle

Manages requirements traceability, change requests, and baselines following BABOK lifecycle practices.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-requirements-lifecycle-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ba-requirements-lifecycle
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/ba-requirements-lifecycle
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill ba-requirements-lifecycle-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Requirements change constantly during a project, and without formal traceability and change control, teams lose track of what was approved, what changed, and why. This Skill governs the full requirements lifecycle so every requirement stays traceable from business need to implementation and test. ## Core Features & Use Cases - Traceability Matrix (RTM): Builds and maintains a matrix linking each requirement to its origin, component, test case, and lifecycle state across 10 defined states. - Change Request Management: Documents CRs with impact analysis covering scope, schedule, cost, quality, and tests, plus governance decisions (approve, reject, defer). - Baseline Control: Creates versioned baselines (initial, sprint, release) so scope creep is measurable and modifications require formal CRs. - Use Case: A stakeholder requests changing an approved business rule mid-project. Use this Skill to document the CR, assess impact on related requirements and tests, route it through governance, and update the RTM and baseline accordingly. ## Quick Start Ask the assistant to run the ba-requirements-lifecycle step to build a traceability matrix and process pending change requests for the current work package.

Frequently Asked Questions about ba-requirements-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a requirements traceability matrix?▼

Build a traceability matrix in four steps: link each requirement to its business need ID, assign design components after technical design, associate test cases, and keep lifecycle states updated as work progresses. The Skill provides a full RTM template with 10 requirement states.

What is the change request process for requirements in BABOK?▼

The change request process has six steps: identify the change, document a CR with justification, analyze impact on requirements and tests, evaluate priority, get a governance decision from the sponsor or CCB, and update artifacts if approved.

When should I create a requirements baseline?▼

Create a baseline when Must Have specifications are complete, at the start of each sprint, when planning a release, or after a major approved change request. Baselines are versioned and never modified retroactively; changes require a formal CR.

When should I not use formal requirements lifecycle management?▼

Skip formal lifecycle management when no requirements are documented yet, since elicitation and analysis must come first, or when the project is small enough that formal traceability would be excessive overhead relative to its value.

What are the signs of a poorly managed traceability matrix?▼

Warning signs include over 20% of requirements lacking a business need ID, missing test cases late in development, states stuck at Implemented without verification, CRs approved without RTM updates, and the matrix existing only in a private local file.