completion-promise

You verify session completion by enforcing a verifiable Completion Promise through a CLI workflow using cs-status, cs-promise, and cs-verify commands to validate per-criterion acceptance criteria before stopping a session.

A completion promise is a file-based session state mechanism that tracks user goals, epics, and features by attaching verifiable evidence to each acceptance criterion, enabling iterative progress validation across multiple session iterations and PRD references.

Stop gates are configured by creating a structured completion promise with acceptance criteria tied to your goals, then using the cs-verify CLI command to enforce completion validation, ensuring session stoppage only occurs when all criteria are demonstrably achieved.

Yes, file-based session state supports per-criterion validation by allowing you to extract goals, create a structured completion promise, and attach evidence to individual epics and features for iterative progress tracking.

Evidence-based verification is managed through a CLI workflow that records progress against acceptance criteria, requiring per-criterion validation and a file-based completion promise to ensure goals are demonstrably achieved before session stoppage.

No external dependencies are required. Completion promise verification operates using a file-based session state and a CLI workflow with cs-status, cs-promise, and cs-verify commands to manage and validate acceptance criteria independently.