skills.rest
jdm4pku
jdm4pkuCOMMUNITY
Explore all skills by this author →
GitHub

change-control-advisor

Evaluate requirements change requests through structured impact analysis and CCB decision workflows.

23|1|Updated Mar 19, 2026
Search Tags:#scope creep#impact analysis#baseline#requirements management#ccb#change control#change request
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill change-control-advisor-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-control-advisor
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/change-control-advisor
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill change-control-advisor-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Baselined requirements attract constant change requests, and without a structured evaluation process projects suffer scope creep, unassessed schedule impacts, and invisible scope growth. This Skill guides you through evaluating each change request with impact analysis, approval decisions, and implementation tracking. ## Core Features & Use Cases - Structured Change Evaluation: Classify changes by type, impact size, and urgency through guided questions, then perform six-step impact analysis covering traceability, schedule, cost, quality, and scope. - CCB Decision Support: Prepare recommendations for the Change Control Board with documented rationale, decision options, and implementation plans. - Scope Creep Detection: Identify warning signs like rising change volume and process bypassing, with concrete response steps. - Use Case: A stakeholder proposes changing a chemical inventory alert from 30 to 45 days mid-development. Use this Skill to trace affected requirements and test cases, estimate effort, and produce an approval recommendation for the CCB. ## Quick Start Use the change-control-advisor skill to evaluate this proposed requirements change and prepare an impact analysis with a CCB recommendation.

Frequently Asked Questions about change-control-advisor

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

FAQPage Schema
How do I evaluate a requirements change request?▼

Classify the change by type (scope addition, modification, deletion, clarification), assess impact size, and rate urgency. Then trace affected requirements and test cases, estimate schedule and cost impact, and prepare an approve, defer, or reject recommendation for the Change Control Board.

What is impact analysis in change control?▼

Impact analysis traces which requirements, test cases, and design components a change affects, then estimates schedule, cost, quality, and scope consequences. It uses requirements traceability links to find downstream dependencies before a change is approved.

How do I detect and stop scope creep in a project?▼

Watch for rising change request volume, changes untraceable to business objectives, and stakeholders bypassing the process. Respond by presenting cumulative change data to the CCB, showing the delta from the original baseline, and re-prioritizing all requirements.

When should a change request not require full CCB review?▼

Clarifications that add detail without changing behavior can be approved by the business analyst alone. Scale the process to the change: scope additions need CCB review, while minor corrections use lightweight approval to avoid process bypass.

What attributes should a change request document include?▼

Capture a unique CR ID, title, requester, submission date, affected requirement IDs, justification, business value, impact assessment, priority, status, decision, decision date, and decision rationale. These attributes make every change visible and auditable.

Related Skills

Explore More Product & Management Skills→
vmitsarasvmitsaras

scope-creep-guard

Classifies proposed project additions as required, justified, deferred, or rejected against an agreed goal.

Community
Intermediate
NestorMonroyNestorMonroy

ba-requirements-lifecycle

Manages requirements traceability, change requests, and baselines per BABOK lifecycle management.

Community
Intermediate
cuiosscuioss
4

traceability

Enforce bidirectional traceability between specifications, code, and tests.

Official
Advanced
nesnilnehcnesnilnehc
7

align-backlog

Map backlog items to strategic anchors and generate a Backlog Alignment Report.

Community
Advanced