Add Spec Impact extension to community catalog#2163
Open
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Open
Add Spec Impact extension to community catalog#2163Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Conversation
Adds spec-kit-impact: blast radius analysis for spec changes. 4 commands: - /speckit.impact.analyze — show what breaks before changing a requirement - /speckit.impact.map — generate requirement dependency graph - /speckit.impact.score — calculate risk score for proposed changes - /speckit.impact.changelog — auto-generate changelog from spec diffs 1 hook: before_specify (pre-change impact analysis) Enables proactive change management for spec-driven teams.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the Spec Impact community extension to Spec Kit’s community catalog and surfaces it in the root README’s community extensions table.
Changes:
- Added a new
impactextension entry toextensions/catalog.community.json(metadata, links, tags, requirements). - Updated the top-level catalog
updated_attimestamp. - Added a “Spec Impact” row to the community extensions table in
README.md.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds the “Spec Impact” row to the community extensions list. |
| extensions/catalog.community.json | Adds the impact extension entry and bumps catalog timestamps. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds Spec Impact — blast radius analysis for spec changes. Shows what code breaks, which tests
fail, and which features are affected BEFORE you change a requirement.
Extension repo: https://github.com/Quratulain-bilal/spec-kit-impact-
The Problem
Changing a spec requirement today can silently break features, tests, and downstream specs across the
entire project. Without impact analysis, every spec change is a gamble — you find out what broke after
you've already broken it.
What Spec Impact Does
4 commands that answer "what happens if I change this?" before you change it:
/speckit.impact.analyze|
|
/speckit.impact.map| Visual dependency graph with risk clusters and single points of failure ||
/speckit.impact.score| Quantitative 0-100 risk score with go/no-go recommendation ||
/speckit.impact.changelog| Auto-generate changelog from spec diffs for stakeholders |1 hook:
before_specify(impact analysis before modifying existing specs)Why This Matters
.specify/directories in the projectChecklist
extension.ymlfollows schema v1.0fleetanditerate)Spec DiagramandSpec Refine)updated_atbumped monotonically (2026-04-11T00:00:00Z)extension.ymlreferences