finish-task

Generate a closeout report and update memory artifacts for completed tasks.

9|1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/conn-castle/agent-layer --skill finish-task-conn-castle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finish-task
Source: https://github.com/conn-castle/agent-layer/tree/main/internal/templates/skills/finish-task
Command: npx skills add https://github.com/conn-castle/agent-layer --skill finish-task-conn-castle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow streamlines the closeout process after implementation by producing a concise, auditable summary and updating relevant memory artifacts.

Core Features & Use Cases

  • Close out completed tasks: generate a structured final report and curate memory state.
  • Selective memory updates: remove resolved items from backlog and maintain only changed context.
  • Lightweight verification: perform fast checks to validate task completion before handoff.

Quick Start

Run the finish-task workflow on the latest finalized task to generate a formal closeout report.

Frequently Asked Questions about finish-task

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

FAQPage Schema
How do I generate a verifiable closeout report after finishing a coding task?

A task closeout workflow generates a concise, auditable summary by verifying the git working tree and plan artifacts, then writes the final report to .agent-layer/tmp/finish-task.<run-id>.report.md.

How does selective memory curation work when closing out a repository task?

Selective memory curation updates project memory artifacts by removing resolved items from the backlog and preserving only changed context. This maintains accurate memory files after task completion.

Do I need existing plan and task artifacts to use an automated task closeout workflow?

Yes, the closeout workflow requires existing plan and task artifacts within the git working tree. These inputs provide the context needed to generate the final report and perform lightweight verification.

Can I run task closeout workflows in a multi-agent environment?

Yes, the task closeout workflow supports multi-agent roles. It allows different agents to coordinate by validating task completion and generating the final structured report.

What is the best way to validate task completion before handing off to another agent?

The best way to validate task completion is a lightweight verification pass that checks the git working tree against plan artifacts. This fast check confirms the task is finished before handoff.

Why does my task closeout process fail to find the final report file?

The workflow writes the final report to .agent-layer/tmp/finish-task.<run-id>.report.md. Check that the run-id is correct and the workflow has write access to the .agent-layer/tmp directory.