task-closure

Verifies task completion against nine evidence-based dimensions and returns a single closure verdict.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/sebaperiesdigit-create/Peries-Skills-Master --skill task-closure-sebaperiesdigit-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: task-closure
Source: https://github.com/sebaperiesdigit-create/Peries-Skills-Master/tree/main/.claude/skills/task-closure
Command: npx skills add https://github.com/sebaperiesdigit-create/Peries-Skills-Master --skill task-closure-sebaperiesdigit-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents tasks from being marked done based on assumption or incomplete work by requiring every closure claim to be backed by cited, fresh evidence before issuing a verdict. ## Core Features & Use Cases - Nine-Dimension Audit: Checks requirements, deliverables, validation, assumptions, evidence, approvals, temporary files, unresolved issues, and requester handoff, each with a strict Confirmed / Gap Found / Unknown / Not Applicable status. - Requirement Traceability: Extracts each stated requirement individually and traces it to specific evidence such as file paths, git results, or tool output. - Approval-Gated Actions: Never deletes or modifies anything without explicit per-action user approval, and only saves a report when explicitly requested. - Use Case: After finishing a code change, ask whether the task is ready to close and receive a verdict of COMPLETE, COMPLETE WITH LIMITATIONS, REVIEW REQUIRED, BLOCKED, or INCOMPLETE with the full evidence table. ## Quick Start Ask the assistant to run a closure check on the task you just finished to confirm it is genuinely complete.

Frequently Asked Questions about task-closure

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a task is actually complete before closing it?▼

Run a closure check that audits nine dimensions: requirements, deliverables, validation, assumptions, evidence, approvals, temporary files, unresolved issues, and handoff. Each check must cite concrete evidence like file paths or git output, and the result is a single verdict such as COMPLETE or INCOMPLETE.

What is requirement traceability in a task closure check?▼

Requirement traceability lists each requirement from the original request separately and links it to the specific evidence that satisfies it. The overall requirements status is the worst status among all rows, so one unverified requirement downgrades the whole dimension.

Can the closure check delete temporary files automatically?▼

No. Temporary files are classified as Disposable, Deliverable-adjacent, or Unknown, and deletion only happens after explicit per-action user approval through a scoped confirmation question. Unknown-classified files are never proposed for deletion.

Why does a closure check return REVIEW REQUIRED instead of COMPLETE?▼

REVIEW REQUIRED is returned when no core work is missing but at least one check is Unknown, evidence is stale and unverified, an approval is pending, or an unresolved issue needs a human decision. Stale evidence, such as a validation run before a later file edit, can never support a Confirmed status.

Does the closure report get saved to a file automatically?▼

No. The full report is shown in chat by default, including the traceability table, dimension statuses, and verdict. It is only written to output/task-closure/<task-slug>-closure-report.md when the user explicitly asks.