scope-delta

Translate requirements and doctrine constraints into traceable scope delta artifacts.

26|3|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill scope-delta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-delta
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/scope-delta
Command: npx skills add https://github.com/davidlee/spec-driver --skill scope-delta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

scope-delta clarifies what an agent should change and why, before implementation starts, so requirements, risks, and closure targets remain consistent and traceable.

Core Features & Use Cases

  • Define applies-to scope: attach the change to the exact target requirements/specs, plus contextual constraints and doctrine.
  • Create a delta with traceability: generate or derive a delta from scratch or from an existing backlog item while ensuring consistent context inputs and relations.
  • Enforce revision-first safety: stop early if the workflow requires a revision-first gate and the needed revision artifact is missing, then guide through the correct next steps.
  • Produce delivery bundle artifacts: ensure the required DE/DR/IP sheets exist and update DE to explicitly state applies_to, context, risks, and verification/closure intent.
  • Prepare phases before implementation: run plan-phase creation after drafting design revision, so execution follows a coherent plan.

Quick Start

Use scope-delta to create a scoped delta from a backlog item by telling the AI to run delta creation for ISSUE-123 and then draft the required DR and DE artifacts with explicit applies_to, risks, and closure intent.

Frequently Asked Questions about scope-delta

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

FAQPage Schema
How do I translate project requirements into a traceable scope delta before implementation?

To translate requirements into a traceable scope delta, convert target specs and doctrine constraints into delivery bundle artifacts (DE/DR/IP) while explicitly defining applies_to scope, context inputs, risks, and verification intent.

What is a revision-first gating mechanism for software scope changes?

A revision-first gating mechanism stops implementation early if required design revision artifacts are missing, ensuring requirements and risks are validated before execution phases begin.

Can I enforce traceability for context inputs and risks using spec-driven planning?

Yes, spec-driven planning enforces traceability by mandating updates to DE sheets that explicitly capture applies_to scope, contextual constraints, risks, and verification intent prior to phase creation.

What are the limitations of creating scoped deltas without delivery bundle artifacts?

Without required delivery bundle artifacts like DE, DR, and IP sheets, scoped deltas lack the necessary context, risks, and verification intent to pass revision-first gating for implementation readiness.

Do I need to read workflow and doctrine files to validate project scope changes?

Yes, validating scope changes requires reading workflow, policy, and doctrine files to ensure the delta applies_to target requirements correctly and satisfies revision-first gating constraints.