spec-delta

To write a delta specification without scope drift, use a template-driven structure to codify feature changes, rationale, and acceptance criteria. This enforces research, impact discovery, and iterative drafting for UI and API changes.

A delta spec is a structured document that codifies feature changes and their rationale across docs, planning, and feature specs. You need one when you require precise scope and acceptance criteria to prevent drift and misinterpretation across teams.

You standardize feature specs for UI and API changes by applying a template-driven structure that guides research, impact discovery, and iterative drafting. This produces ready-to-publish specs with clear user stories and integration steps.

Yes, the delta spec workflow includes status updates and review steps. It integrates with a spec-reviewer to enforce acceptance criteria and integration steps, ensuring the specification meets quality standards before publishing.

The best way to document feature rationale and acceptance criteria is through a repeatable process that leverages existing delta docs. It guides iterative refinement and produces ready-to-publish specs in a standardized markdown format.

Yes, you can use delta specs to research and discover the impact of feature changes. The workflow includes specific research prompts and impact discovery phases that leverage existing documentation to inform your iterative drafting.