audit/verify-definition-of-done

Verifying a Definition of Done requires passing the bounded context and session identifier, which triggers checks for git diff, tests, and artifact existence before generating a DoD report.

A Definition of Done report aggregates test and validation results for a bounded context. It is generated by running required DoD checks and writing the output report under runtime/contexts/<context>/audits/dod/.

Yes, you can automate Definition of Done validation in CI-like workflows by providing bounded context, session ID, and test commands to automatically verify session artifacts and emit a DoD report.

Yes, session artifacts are required. The skill validates that the session record and required artifacts exist before running DoD checks and generating the final report.

Required inputs include context, session_id, and commands for tests and DoD checks. Optional artifacts can be provided to ensure the session record exists before reporting.

A Definition of Done verification logs a U.Work record when telemetry is available to support automated traceability of the DoD validation process and artifact checks within the bounded context.