speckit-acceptance

Generate user acceptance documentation by creating acceptance.md, acceptance-checklist.md, and validation.md with evidence-linked steps. This separates AI-verified validation from human product judgment to prepare a feature for sign-off.

Prepare for user sign-off by generating acceptance materials that clearly state observable behavior, validation evidence, and remaining gaps. This provides a concise checklist for users to run and explicitly confirm acceptance.

An evidence-aware acceptance checklist works by separating AI-verified validation from human product judgment. It keeps any validation gaps visible instead of hiding them, ensuring blockers are reported before final user confirmation.

Create acceptance.md and validation.md files during spec-kit delivery stages when implementation is finished. They are needed when human review must confirm validation evidence, observable behavior, and remaining gaps before sign-off.

You can use this workflow with unresolved blockers because it includes blocker reporting within the generated validation documentation. Remaining gaps are kept visible instead of hidden, allowing users to make informed judgments during sign-off.

Spec-kit acceptance generation requires no external dependencies. It functions independently to produce the required acceptance.md, acceptance-checklist.md, and validation.md files with evidence-linked steps for your completed feature.