skills.rest
noelserdna
noelserdnaCOMMUNITY
Explore all skills by this author β†’
𝕏@andresleon79GitHub

req-change

Manage requirements changes with bidirectional propagation across specification documents.

1|Updated Feb 7, 2026
Search Tags:#documentation#requirements#traceability#change-management#impact-analysis#pipeline-cascade#change-plan
One-click install
npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill req-change
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: req-change
Source: https://github.com/noelserdna/claude-plugin-sdd/tree/main/skills/req-change
Command: npx skills add https://github.com/noelserdna/claude-plugin-sdd --skill req-change

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

This Skill manages the full lifecycle of requirements changes and pipeline cascade across the software development lifecycle, ensuring traceability and alignment across the entire specification chain.

Core Features & Use Cases

  • Interactive intake and classification of changes using ISO 14764 maintenance categories.
  • Impact analysis across the REQ β†’ UC β†’ WF β†’ API β†’ BDD β†’ INV β†’ ADR β†’ RN chain.
  • Change planning and atomic execution with downstream cascade to re-plan, re-task, and re-implement affected artifacts.
  • Change reporting and alignment audits to ensure no gaps between requirements and specifications.
  • Governance and traceability management, including updates to CLARIFICATIONS and CHANGELOG.

Quick Start

Prepare a CHANGE-REQUEST.md describing one atomic change, place it under changes/, then run /sdd:req-change --file changes/CHANGE-REQUEST.md. Review the generated Change Plan and approve to execute the cascade.

Frequently Asked Questions about req-change

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

FAQPage Schema
How do I manage requirements changes and cascade them across the software pipeline?β–Ό

Requirements changes are managed by submitting an atomic change request, which triggers impact analysis and downstream cascade across the entire specification chain to ensure traceability and alignment.

What is pipeline cascade in requirements change management?β–Ό

Pipeline cascade is the bidirectional propagation of requirements changes through the specification chain, automatically re-planning, re-tasking, and re-implementing affected downstream artifacts.

How do I perform impact analysis for a requirements modification?β–Ό

Impact analysis is performed automatically by classifying the change and mapping its effects across the REQ, UC, WF, API, BDD, INV, ADR, and RN specification documents.

Can I use a standard markdown file to trigger a change plan?β–Ό

Yes, you prepare a CHANGE-REQUEST.md file describing one atomic change, place it under a changes directory, and run the skill to generate a Change Plan for review and approval.

Does this approach support deprecating requirements without breaking traceability?β–Ό

Yes, deprecating requirements maintains traceability by updating CLARIFICATIONS and CHANGELOG entries while coordinating cross-document execution and validation to prevent alignment gaps.

What is the best way to classify maintenance changes for software specifications?β–Ό

Changes are classified using ISO 14764 maintenance categories during the interactive intake process, ensuring standardized handling of ADD, MODIFY, and DEPRECATE operations across artifacts.

Related Skills

Explore More Software Engineering Skills→
Eigo-Mt-FujiEigo-Mt-Fuji

change-impact-analyzer

Analyze change impact and validate delta specifications for brownfield systems.

Community
Advanced
caelaxiecaelaxie

openspec-verify-change

Validate code implementations against change artifacts using the openspec CLI.

Community
Advanced
noelserdnanoelserdna

traceability-check

Validate SDD artifact traceability and report orphaned or broken references.

Community
Basic
JunrootJunroot
3

revise

Propagate GitHub issue updates across requirements, design, and task stages.

Community
Intermediate