close-change

Close a delta after spec reconciliation, coverage gates, and lifecycle updates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents “done” from being declared too early by ensuring delta closure only happens after contracts/spec reconciliation, required evidence/coverage updates, and repository workflow compliance.

Core Features & Use Cases

  • Pre-checks for phase completion and audit-ready specs: verifies implementation phase/IP criteria are complete and that relevant specs are patched to match contracts and findings.
  • Deterministic delta completion with coverage gating: completes the delta via the workflow’s CLI, handles blocked coverage by fixing owning coverage requirements, and applies --force only with explicit justification.
  • Lifecycle and backlog follow-through: updates owning-record lifecycle/evidence coherence after completion and revisits originating backlog items so statuses and notes don’t drift.

Quick Start

Use the close-change skill to safely complete delta DE-123 by running the command: uv run spec-driver complete delta DE-123.

Frequently Asked Questions about close-change

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

FAQPage Schema
How do I safely close a delta in spec-driven development without missing spec reconciliation?

To safely close a delta, you must pass audit-driven spec reconciliation, satisfy coverage and evidence gates, and update owning-record lifecycles. This enforces a pre-check and preview sequence before completing the delta via deterministic spec-driver commands.

What happens if coverage gates are blocked when completing a delta?

When coverage gates are blocked during delta completion, the workflow handles it by fixing owning coverage requirements. Applying the `--force` flag to bypass gates is only permitted with explicit justification.

When should I use workflow validation gates for delta lifecycle management?

Workflow validation gates are needed when closing implementation deltas to ensure requirements, specs, and backlog links remain coherent. They prevent premature completion by enforcing phase checks and evidence tracking before final closure.

Can I update backlog item statuses automatically after delta closure?

Yes, delta closure includes lifecycle and backlog follow-through. It updates owning-record evidence coherence after completion and revisits originating backlog items to ensure statuses and notes do not drift.

What is the best way to ensure audit-ready specs before completing a delta?

The best way to ensure audit-ready specs is running pre-checks that verify implementation phase criteria are complete and relevant specs are patched to match contracts and findings before triggering delta completion.

Why does my delta completion fail during the pre-check sequence?

Delta completion fails during pre-checks if implementation phase criteria are incomplete or specs are not patched to match contracts and findings. The deterministic workflow enforces these checks before allowing completion.