What is the difference between RD and REQM in this skill?

RD focuses on creating requirements (elicitation and specification), while REQM focuses on maintaining them through change control and traceability throughout the project.

Does this skill work for Agile user stories?

Absolutely. It defines Level 2 compliance as using user stories and acceptance criteria, scaling to more formal templates only when project complexity requires it.

How does this skill help with CMMI compliance?

It provides specific guidance and templates for RD (Requirements Development) and REQM (Requirements Management) process areas across CMMI Levels 2, 3, and 4.

Can I use this with GitHub or Azure DevOps?

Yes, the skill includes specific implementation patterns for platform-native traceability using GitHub Issues, PRs, and Azure DevOps work items.

Requirements Lifecycle Manager

Name: Requirements Lifecycle Manager
Author: tachyon-beep

bytachyon-beep

•

Collaboration Tools

Manages the end-to-end requirements process from initial elicitation and prioritization to change control and traceability.

About

The Requirements Lifecycle skill provides a structured framework for managing software requirements throughout the SDLC, covering both Requirements Development (RD) and Requirements Management (REQM). It guides users through eliciting stakeholder needs without 'gold plating,' resolving conflicts using MoSCoW prioritization, and establishing bidirectional traceability between requirements, design, and tests. Designed to scale across CMMI Levels 2 through 4, it offers practical implementation patterns for modern platforms like GitHub and Azure DevOps, ensuring compliance while minimizing manual documentation overhead.

Key Features

Formal and lightweight change impact analysis templates
10 GitHub stars
Bidirectional Requirement Traceability Matrix (RTM) implementation patterns
Scalable documentation guidance for CMMI Levels 2, 3, and 4
Stakeholder elicitation through structured workshops and interview scripts
MoSCoW and Value/Effort prioritization to prevent scope creep

Use Cases

Stabilizing projects suffering from constant requirement changes and volatility
Resolving stakeholder conflicts with objective decision matrices
Preparing for audits or compliance reviews in regulated industries

About

Key Features

Formal and lightweight change impact analysis templates
10 GitHub stars
Bidirectional Requirement Traceability Matrix (RTM) implementation patterns
Scalable documentation guidance for CMMI Levels 2, 3, and 4
Stakeholder elicitation through structured workshops and interview scripts
MoSCoW and Value/Effort prioritization to prevent scope creep

Use Cases

Stabilizing projects suffering from constant requirement changes and volatility
Resolving stakeholder conflicts with objective decision matrices
Preparing for audits or compliance reviews in regulated industries