spec-change-delivery

Name: spec-change-delivery
Availability: InStock
Author: paradox123

Deliver one bounded change from a requirements spec with verification gates.

Updated Jan 23, 2026

Search Tags:#verification #handoff #OpenSpec #scope-control #spec-change #change-delivery

Ready to run

npx skills add https://github.com/paradox123/shared-ai-docs --skill spec-change-delivery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-change-delivery
Source: https://github.com/paradox123/shared-ai-docs/tree/main/skills-repo/skills/spec-change-delivery
Command: npx skills add https://github.com/paradox123/shared-ai-docs --skill spec-change-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables teams to execute exactly one bounded change from a formal requirements spec, preventing scope creep and delivering clear, verifiable outcomes.

Core Features & Use Cases

One-change-per-run discipline ensures focused delivery and easier verification.
Explicit DoR/DoD gates and a kickoff contract to prevent scope drift.
Optional OpenSpec mode or direct execution with evidence-based READY/NOT READY verdicts.

Quick Start

Provide a single, well-scoped change request and run the delivery flow in direct mode.

Frequently Asked Questions about spec-change-delivery

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

FAQPage Schema

How do I deliver a single bounded change from a requirements spec without scope creep?▼

Spec change delivery applies a one-change-per-run discipline with explicit DoR/DoD gates and a kickoff contract to prevent scope drift. It outputs handoff-ready evidence with a READY or NOT READY verdict.

What is a DoR and DoD gate in spec change delivery?▼

DoR (Definition of Ready) and DoD (Definition of Done) gates are explicit checkpoints in the change delivery flow. They verify scope boundaries before execution and validate completion before handoff.

How do I verify a spec change has met acceptance requirements?▼

Spec change delivery includes explicit verification commands to prove acceptance. It generates evidence-based READY or NOT READY verdicts to confirm the bounded change satisfies formal requirements.

Can I execute a spec change without using OpenSpec?▼

Yes, spec change delivery supports optional OpenSpec mode or direct execution mode. You can provide a single, well-scoped change request and run the delivery flow directly without mandatory OpenSpec integration.

Why does my spec change delivery fail to stay within the original requirements?▼

Scope drift occurs without a kickoff contract and one-change-per-run discipline. Spec change delivery enforces these boundaries, ensuring exactly one bounded change is planned and delivered with verifiable outcomes.

Does spec change delivery work for large requirements specs with multiple changes?▼

Spec change delivery enforces a one-change-per-run discipline, meaning it processes exactly one bounded change at a time. For multiple changes, run separate delivery flows for each discrete task.