review-work

To verify completed work against acceptance criteria, compare the thread's deliverables directly against its backing plan references. This ensures every acceptance criterion is explicitly met with measurable evidence, flagging any misalignments or gaps before handoff.

Plan alignment verification for engineering and deploy tasks is the process of checking completed thread work against its backing plan. It derives acceptance criteria from plan references to identify misalignments and gaps across ops, email, payments, and identity domains.

You can check rule compliance across ops, deploy, and payments domains by evaluating the completed work against the backing plan. The process requires explicit acceptance criteria coverage and self-verification evidence like test outputs or API responses.

Work verification requires measurable evidence rather than prose descriptions. You must provide self-verification proofs such as test outputs, query results, API responses, or screenshots to explicitly meet acceptance criteria before human QA begins.

You should not rely on human QA without self-verification evidence first. Human QA serves as the final polishing layer, meaning you must generate measurable proofs like test outputs and logs to ensure rule compliance and full acceptance criteria coverage beforehand.

The best way to flag misalignments and gaps in completed thread work is to cross-reference deliverables against the backing plan's acceptance criteria. This requires rule-compliance checks and explicit coverage to identify missing self-verification evidence accurately.