change-request-analysis

Draft and evaluate Change Requests with problem statements and acceptance criteria.

Updated Feb 28, 2026

Search Tags:#requirements #risk-assessment #change-management #stakeholder-communication #cr-analysis #scope-estimation

Ready to run

npx skills add https://github.com/dsivov/ai_development_team --skill change-request-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-request-analysis
Source: https://github.com/dsivov/ai_development_team/tree/main/.claude/skills/change-request-analysis
Command: npx skills add https://github.com/dsivov/ai_development_team --skill change-request-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Change Requests are often vague, leading to misaligned expectations and delays. This Skill provides a structured approach to drafting, evaluating, and scoping CRs to ensure clarity, traceability, and faster delivery.

Core Features & Use Cases

Structured CR template: Defines problem, scope, acceptance criteria, and impact to guide technical design and implementation.
Scope estimation & risk assessment: Provides sizing guidance and red flags to prevent scope creep.
CR workflow guidance: Guides open → in_progress → completed → closed lifecycle and ownership assignments.

Quick Start

Draft a CR with a clear problem statement, measurable acceptance criteria, and defined impact.

Frequently Asked Questions about change-request-analysis

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

FAQPage Schema

How do I write a change request with clear scope and acceptance criteria?▼

A change request prevents scope creep by combining a clear problem statement, measurable acceptance criteria, and impact assessment. This structured approach ensures technical design aligns with stakeholder expectations and prevents vague requirements.

What should be included in a change request risk assessment?▼

A change request risk assessment should include sizing guidance, impact evaluation, and scope creep red flags. Identifying these risks early helps justify the defined scope and ensures smoother delivery across product and engineering initiatives.

How do I manage the change request workflow from open to closed?▼

Managing a change request workflow involves tracking its lifecycle from open to in_progress, completed, and closed. Assigning clear ownership at each stage ensures traceability and faster delivery of product and engineering initiatives.

Why do vague change requests cause delivery delays and misaligned expectations?▼

Vague change requests cause delays because they lack defined problem statements and measurable acceptance criteria. Without structured scope estimation and impact assessment, technical design and implementation suffer from misaligned stakeholder expectations.

Can I use a structured change request template for product, design, and engineering initiatives?▼

Yes, a structured change request template applies across product, design, and engineering initiatives. It standardizes problem statements, acceptance criteria, and impact assessments to ensure clarity and traceability throughout the project lifecycle.