requirements_assess_changes

Assess change requests by evaluating impact, risks, and recommended actions.

40|15|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/chaussky/ainalyst --skill requirements-assess-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements_assess_changes
Source: https://github.com/chaussky/ainalyst/tree/main/skills/requirements_assess_changes
Command: npx skills add https://github.com/chaussky/ainalyst --skill requirements-assess-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured methodology to evaluate Change Requests (CRs) by tracing impact, assessing risk, and guiding governance decisions.

Core Features & Use Cases

  • Open CRs and capture formal details, initiating the four-stage pipeline: open_cr, run_cr_impact, score_cr, and resolve_cr.
  • Automatically analyze impact by traversing the 5.1 graph to identify affected requirements, tests, and code areas.
  • Compute the CR score across five axes (Benefit, Cost, Impact, Schedule, Urgency) and surface a preliminary recommendation with automated checks.
  • Generate an auditable CR decision record and prepare communication artifacts for stakeholders.

Quick Start

Open a CR, run impact analysis, score the CR, and resolve with an approved decision using the MCP tools.

Frequently Asked Questions about requirements_assess_changes

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

FAQPage Schema
How do I assess a change request for impact and risk across product lines?

Assess change requests by tracing impact, evaluating risks, and guiding governance decisions using a four-stage pipeline: open_cr, run_cr_impact, score_cr, and resolve_cr. This applies to new, modified, or regulatory CRs across projects.

What is a CR score and how is it calculated for governance decisions?

A CR score evaluates change requests across five axes: Benefit, Cost, Impact, Schedule, and Urgency. It surfaces a preliminary recommendation with automated checks to guide governance workflows and stakeholder communication.

How do I run impact analysis to identify affected requirements and code areas?

Run impact analysis by traversing the 5.1 graph to identify affected requirements, tests, and code areas. This automated traversal maps dependencies within the CR pipeline to ensure comprehensive impact coverage.

Can I generate an audit trail for stakeholder communication after resolving a change request?

Yes, you can generate an auditable CR decision record and prepare communication artifacts for stakeholders. The resolve_cr stage produces these results, ensuring formal documentation throughout the governance workflow.

Does this change request assessment pipeline work for regulatory CRs?

Yes, the structured assessment methodology explicitly applies to regulatory CRs, alongside new and modified change requests. It evaluates impact, risks, and recommended actions across all CR types within governance workflows.