ac-lock

You can consolidate acceptance criteria by extracting, deduplicating, and categorizing them from PRD, TechSpec, and Tasks into a single locked set. This ensures cross-document alignment and requires explicit user confirmation before implementation starts.

Locking acceptance criteria prevents scope drift by consolidating them into an authoritative set with provenance sources. This requires explicit user confirmation, ensuring all cross-document alignment is verified before development starts.

You persist locked acceptance criteria by saving them to the .claude/feature-state/{slug}/accepted-criteria.md file. This file stores the consolidated list complete with provenance sources for full traceability during quality assurance.

Yes, acceptance criteria locking is designed specifically for feature workflows where cross-document alignment is essential. It ensures extraction, deduplication, and categorization of criteria from PRD, TechSpec, and Tasks before implementation begins.

The best way to manage acceptance criteria across multiple documents is consolidating them into a single locked set before implementation. This process extracts, deduplicates, and categorizes criteria from PRD, TechSpec, and Tasks for user confirmation.

Yes, explicit user confirmation is required to lock acceptance criteria before implementation begins. The process presents the consolidated criteria from PRD, TechSpec, and Tasks to the user for final approval and persistence.