Add Spec Scope extension to community catalog#2172
Open
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Open
Add Spec Scope extension to community catalog#2172Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Conversation
Adds spec-kit-scope: effort estimation and scope tracking from spec artifacts. 4 commands: - /speckit.scope.estimate — data-driven effort estimation with three-point ranges - /speckit.scope.compare — side-by-side spec scope comparison - /speckit.scope.creep — scope creep detection via git history - /speckit.scope.budget — sprint-ready time budget generation 1 hook: after_specify (auto-estimation) Turns "how long will this take?" into a data-driven answer.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the Spec Scope community extension to the Spec Kit community catalog so users can discover and install it from the standard listings.
Changes:
- Added a new “Spec Scope” row to the community extensions table in
README.md. - Added a new
"scope"entry toextensions/catalog.community.json(including metadata, URLs, tags, requirements), and bumped the catalogupdated_attimestamp.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds “Spec Scope” to the human-readable community extensions list. |
| extensions/catalog.community.json | Registers the “scope” extension in the machine-readable community catalog and updates updated_at. |
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 Scope — effort estimation and scope tracking from spec artifacts. Turns "how long will
this take?" from a guess into a data-driven answer.
Extension repo: https://github.com/Quratulain-bilal/spec-kit-scope-
The Problem
After writing a spec, the first question is always "how long?" Today the answer is a guess. Nobody
tracks how much a spec has grown. Scope creep happens silently. Sprint planning ignores spec
complexity.
What Spec Scope Does
4 commands that turn specs into project estimates:
/speckit.scope.estimate/speckit.scope.compare/speckit.scope.creep/speckit.scope.budget1 hook:
after_specify(auto-generate estimate after writing spec)Why This Matters
Checklist
extension.ymlfollows schema v1.0security-reviewandship)Spec RefineandSpec Sync)updated_atbumped monotonically (2026-04-11T10:00:00Z)extension.ymlreferences