Skip to content

Add Spec Scope extension to community catalog#2172

Open
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Quratulain-bilal:feat/scope-extension
Open

Add Spec Scope extension to community catalog#2172
Quratulain-bilal wants to merge 1 commit intogithub:mainfrom
Quratulain-bilal:feat/scope-extension

Conversation

@Quratulain-bilal
Copy link
Copy Markdown
Contributor

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:

Command Purpose
/speckit.scope.estimate Complexity scoring + three-point effort estimates
(optimistic/realistic/pessimistic)
/speckit.scope.compare Compare two specs to quantify scope differences and effort impact
/speckit.scope.creep Detect scope creep by comparing current spec against git history with
timeline
/speckit.scope.budget Generate time budget with hours per phase, overhead, and sprint fit
analysis

1 hook: after_specify (auto-generate estimate after writing spec)

Why This Matters

  • Data-driven estimates from actual spec content, not gut feelings
  • Scope creep detection with timeline showing exactly when and what crept in
  • Sprint fit analysis: does the spec fit available hours? If not, suggests trade-offs
  • Transparent methodology: shows scoring formula so estimates can be challenged
  • All commands are read-only

Checklist

  • Extension repo published with v1.0.0 tag
  • extension.yml follows schema v1.0
  • Description under 100 characters (93)
  • Catalog entry alphabetically ordered (between security-review and ship)
  • README row alphabetically ordered (between Spec Refine and Spec Sync)
  • updated_at bumped monotonically (2026-04-11T10:00:00Z)
  • Entry timestamps set to current time
  • JSON validated
  • All 4 command files match extension.yml references
  • README, CHANGELOG, LICENSE included

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.
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 to extensions/catalog.community.json (including metadata, URLs, tags, requirements), and bumped the catalog updated_at timestamp.
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants