w05-task-closure

Original：🇨🇳 Chinese

Translated

1 scriptsChecked / no sensitive code detected

Task Closure Specification, including log generation and optimization analysis. Applicable to the closure phase after major deliverables are completed.

2installs

Sourceqiao-925/qiao-skills

Added on2026-02-08

NPX Install

npx skill4agent add qiao-925/qiao-skills w05-task-closure

SKILL.md Content (Chinese)

View Translation Comparison →

Task Closure Specification

Applicable to the closure phase after major deliverables are completed, ensuring logs and optimization analysis are fully implemented.

⚠️ Core Mandatory Requirements

Trigger Conditions

Major functions or document deliverables have been completed
User explicitly instructs "Enter closure/post-process"
Consent is obtained after the Agent delivers the summary and asks for confirmation

Mandatory Processes

W00 Synchronization Check: Confirm that the final issue synchronization (including the final checkpoint summary and next-step information) has been completed via
```
w00-workflow-checkpoint
```
.
Structure Check (Final Closure): All code files involved in this task must be ≤300 lines (
```
file-size-limit
```
), with clear responsibilities and no circular dependencies (
```
single-responsibility
```
). If exceeding the limit or with unclear responsibilities: split/refactor first before proceeding with closure; if the user chooses to postpone handling, record "Outstanding: Structural Issues" and suggestions in the log.
Generate Task Log: Use
```
scripts/generate_task_log.py
```
Six-Dimension Optimization Analysis: Code Quality/Architecture Design/Performance/Testability/Maintainability/Technical Debt

If no Issue is bound, clearly record the reason and plan for supplementing the Issue in the closure description, and supplement an alternative tracking method for the project-level task view.

AI Agent Behavioral Requirements

Proactive Inquiry

After completing major deliverables, proactively ask:

Major deliverables have been completed. Would you like to proceed to the closure process?

Completion Report

After completing the closure, report the log location and key analysis points.

Collaboration with W00 (Automatic + Manual)

Before closure, check if there is a bound
```
Issue #
```
.
If exists: Directly execute task closure via
```
w05-task-closure
```
; if necessary, only call
```
w00-workflow-checkpoint
```
to supplement the final checkpoint archive.

Prohibited Items

❌ Skip the closure process or falsify execution results
❌ Omit core log fields or six-dimension analysis
❌ Fail to explain the reasons and plans for unexecuted items

Tool Scripts

Script:

scripts/generate_task_log.py

Function: Generate standardized task logs, including six-dimension optimization analysis

Reference Materials

```
references/closure-workflow.md
```
- Detailed description of the closure workflow (trigger conditions, structure check, log specification, six-dimension analysis)
```
../w00-workflow-checkpoint/SKILL.md
```
- Workflow GitHub Issues basic archiving capability (Automatic + Manual)
```
refactor-and-decompose/SKILL.md
```
- Structure check constraints before closure