Add Spec Scope extension to community catalog

[Quratulain-bilal]

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