From f87db70f7850a0eef69d4c10cade238def61f52d Mon Sep 17 00:00:00 2001 From: Julian Lechner Date: Thu, 24 Sep 2026 19:12:30 +0200 Subject: [PATCH] docs(skill): clarify work item verification triggers --- .../verification/work-item-verification/SKILL.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/shared/skills/verification/work-item-verification/SKILL.md b/shared/skills/verification/work-item-verification/SKILL.md index 7a26cdc..3818387 100644 --- a/shared/skills/verification/work-item-verification/SKILL.md +++ b/shared/skills/verification/work-item-verification/SKILL.md @@ -1,10 +1,18 @@ --- name: work-item-verification -description: Verify that a work item meets its stated acceptance criteria. +description: 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 -Compare the completed change with its requirements and acceptance criteria. +Use when deciding whether a completed change satisfies a defined work item or review request. -Return passed criteria, failed criteria, checks run, and remaining limitations. +## Workflow + +1. Read the objective, scope boundaries, acceptance criteria, and material constraints. +2. Map each criterion to direct evidence: changed files, observable behavior, command output, test result, or user-confirmed outcome. +3. Mark each criterion as met, unmet, or unverified. Do not treat a successful build as proof of unrelated behavioral criteria. +4. Confirm the implementation stayed within scope and did not leave generated output, documentation, or consumers inconsistent. +5. 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.