skills.rest
Longhuiberkeley
LonghuiberkeleyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specflow-change-impact-review

Scan unreviewed DEC artifacts, compute blast radius, and file CHL findings.

2|Updated Apr 18, 2026
Search Tags:#automation#audit#artifact#blast-radius#change-impact#dec
One-click install
npx skills add https://github.com/Longhuiberkeley/specflow --skill specflow-change-impact-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specflow-change-impact-review
Source: https://github.com/Longhuiberkeley/specflow/tree/main/.claude/skills/specflow-change-impact-review
Command: npx skills add https://github.com/Longhuiberkeley/specflow --skill specflow-change-impact-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the discovery and auditing of change impact by identifying unreviewed DEC artifacts, computing their blast radius, and surfacing findings as CHLs to maintain traceability and quality in the change process.

Core Features & Use Cases

  • Discovery of unreviewed DEC artifacts in _specflow/work/decisions/ and detection via review_status: unreviewed.
  • Blast-radius calculation via the DEC's ID and artifacts it addresses; uses the specflow change-impact workflow to focus review.
  • Filing findings as CHLs and updating DEC status to reflect results while ensuring idempotent behavior.

Quick Start

Run the change-impact reviewer workflow on unreviewed DEC artifacts to auto-generate CHLs for issues.

Frequently Asked Questions about specflow-change-impact-review

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

FAQPage Schema
How do I automate the review of unreviewed change records and calculate their blast radius?▼

Automating change impact review involves scanning _specflow/work/decisions/ for artifacts with review_status: unreviewed, computing their blast radius via DEC IDs, and analyzing impacted artifacts against architectural constraints to file findings as CHLs.

What is the best way to ensure idempotent operation when auditing change impact for decision artifacts?▼

Idempotent change impact auditing is achieved by automatically skipping already processed DECs, ensuring that reviewed or flagged decision artifacts are not re-evaluated, which prevents duplicate findings and maintains stable traceability.

How does change impact review handle decision artifacts that violate architectural constraints?▼

Change impact review handles architectural constraint violations by analyzing the impacted artifacts within the blast radius and filing the discovered issues as CHLs linked to the source DEC, updating its status to flagged.

When do I need to compute the blast radius of a decision artifact in a specflow workflow?▼

You need to compute the blast radius of a decision artifact when its review_status is unreviewed, allowing you to identify the full impact cone of artifacts it addresses before analyzing them against architectural constraints.

Can I use change impact review to maintain traceability across unreviewed DECs and their impacted artifacts?▼

Yes, change impact review maintains traceability by linking filed CHL findings directly to the source DEC and updating the DEC status to reviewed when clean or flagged when issues are found across the impacted artifacts.

Why does my change impact audit skip certain decision artifacts during the review process?▼

Your change impact audit skips certain decision artifacts to ensure idempotent operation, automatically bypassing DECs that have already been processed and had their status updated to reviewed or flagged.

Related Skills

Explore More Software Engineering Skills→
synaptiaisynaptiai
6

generating-constrained-specs

Generate PRD and architecture documents with mandatory DEC-* decision citations.

Official
Advanced
jmaglyjmagly
175

architecture-evolution

Analyze architecture change impact and generate ADRs and migration plans.

Community
Advanced
FernanSuozaFernanSuoza

gov-change-impact-analyzer

Analyze change impacts across requirements, design, stories, tests, and release scope.

Community
Advanced
gao-hongnangao-hongnan
3

review-contract

Standardize code review findings into a canonical JSON schema.

Community
Advanced