1.3 KiB
1.3 KiB
name, description
| name | description |
|---|---|
| work-item-verification | Use when checking whether completed work satisfies explicit scope, constraints, and acceptance criteria; map each criterion to evidence and mark it met, unmet, or unverified. |
Work Item Verification
Use when deciding whether a completed change satisfies a defined work item or review request.
Workflow
- Read the objective, scope boundaries, acceptance criteria, and material constraints.
- Map each criterion to direct evidence: changed files, observable behavior, command output, test result, or user-confirmed outcome. For criteria relying on external technology behavior, MUST apply the verification checkpoint in
technical-research; check the actual supporting sources and version against the implementation, not merely whether a lookup occurred. - Mark each criterion as met, unmet, or unverified. Do not treat a successful build as proof of unrelated behavioral criteria.
- Confirm the implementation stayed within scope and did not leave generated output, documentation, or consumers inconsistent.
- Record known limitations, unresolved decisions, and checks that could not run.
Return a criterion-by-criterion result with evidence and a concise completion status. Do not claim completion while a required criterion remains unmet or unverified.