validating-completed-tasks
Installation
SKILL.md
Validating Completed Tasks
Determine whether the delivered work actually satisfies the task, whether its conclusions or behavior can be trusted, and what remains before acceptance. Review, real verification, and an author-facing report are one workflow; passing unit tests or a plausible document alone does not answer the question.
Scope and Authority
Use for implementations, research/security reports, or mixed deliverables. This is a coordinator, not another review method or report template. Load the owner skill for each applicable stage below; reuse it if already loaded. Refer to its resources from that skill's actual loaded directory, not guessed installation paths or sibling folders. Do not rely on an agent profile to load the method.
| Stage | Owner and when to use it |
|---|---|
| Code inspection and findings | reviewing-code-changes before inspecting a change. It owns scope, whole-change coverage, conformance, design/defect review, finding validation, severity, and readiness. Use its references/requirements.md when task requirements exist, references/scope-and-evidence.md for the comparison cases it covers, and references/test-design.md when designing checks. |
| Research claim validation | research-with-evidence before substantive investigation of a delivered report. It owns source fitness, claim provenance, counterevidence, quantitative claims, and research coverage. This skill adds the task-completeness check. |
| Code-review report | writing-code-review-reports once results exist, before drafting the requested/default report. It owns report structure, classifications, extras/minor/baseline sections, language, evidence, and safe delivery; use its Persian or consolidation reference when applicable. |