speckit-scope-compare

Compare two Specify spec versions and quantify requirement scope changes.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-scope-compare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-scope-compare
Source: https://github.com/B0yZ4kr14/OrthoPlus-Enterprise/tree/main/.specify-backups/20260518-141826/_agents/skills/speckit-scope-compare
Command: npx skills add https://github.com/B0yZ4kr14/OrthoPlus-Enterprise --skill speckit-scope-compare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes guesswork when comparing two spec versions by turning requirement changes into measurable scope deltas and effort implications.

Core Features & Use Cases

  • Spec-to-spec comparison: compares two specs or two versions of the same spec side-by-side.
  • Quantified scope delta: reports numeric changes across requirements, scenarios, success criteria, task items, and external integrations, including a complexity score delta.
  • Effort-linked impact: translates scope changes into an estimated additional effort for optimistic, realistic, and pessimistic scenarios.
  • Git-aware workflow: supports comparing against any git ref (branch, tag, commit hash) and labels Version A vs Version B explicitly.

Use case: when a product team revises a dental workflow spec, you can quickly see whether the change mainly adds new requirements, removes obligations, or modifies complexity—so planning stays accurate.

Quick Start

Ask the AI to compare your current spec against a previous git ref and return a full scope delta report in markdown, labeling the older version as Version A and the current version as Version B.

Frequently Asked Questions about speckit-scope-compare

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

FAQPage Schema
How do I quantify effort impact when comparing two spec versions?

Spec comparison quantifies effort impact by calculating numeric scope deltas across requirements, scenarios, and tasks, then translating those changes into optimistic, realistic, and pessimistic effort estimates.

Can I compare requirement changes across different git branches?

Yes, you can compare requirement changes against any git ref including branches, tags, and commit hashes. The comparison explicitly labels the older git ref as Version A and the current spec as Version B.

What is the best way to calculate scope delta for modified requirements?

Scope delta calculation categorizes requirement-level differences into added, removed, modified, and matched items, generating a numeric complexity score delta to measure the exact scope change between spec versions.

Does spec comparison work with plan.md and tasks.md files?

Yes, spec comparison optionally includes plan.md and tasks.md files in the scope delta analysis to provide a comprehensive view of requirement changes and their downstream effort implications.

How do I generate a scope delta report for spec planning?

Ask the AI to compare your current spec against a previous git ref to return a full scope delta report in markdown, detailing requirement differences, complexity scores, and estimated additional effort.