# Task Closeout > Capture the current task into a structured temporary session bundle under `.agents/sessions/` so a learning agent can later distill durable repo knowledge. Use for completed, blocked, or abandoned tasks with meaningful changes, debugging, validation, or reusable lessons. - Skill: `hypercubed/task-closeout` (Agent Skill, multi-file: 8 files) - Install (CLI): `npx skillmds@latest add hypercubed/task-closeout` - Raw SKILL.md: https://api.skillmd.com/api/skills/hypercubed/task-closeout/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: Hypercubed (https://skillmd.com/u/hypercubed) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/hypercubed/task-closeout --- # Task Closeout ## Goal Create a temporary handoff packet for later learning extraction. Follow **Skill initialization** and **Procedure** below. Required filenames, `summary.json` expectations (including `openspec_change`), and write scope are in [`CONTRACT.md`](CONTRACT.md). ## Skill initialization (before first closeout) Run this once per target repo after the skill files are present under `.agents/skills/task-closeout/` (for example after copying only that skill folder or after an `npx`/package install drops it there). Idempotent: safe to repeat. 1. Resolve the repo root (the directory that contains `.git/` in normal layouts). 2. Ensure `.agents/sessions/` exists. 3. If `.agents/sessions/README.md` is missing, create it from `bootstrap/sessions/README.md` in this skill folder. 4. Ensure `.agents/.gitignore` exists. If it is missing, create it with exactly: ```gitignore sessions/* !sessions/README.md ``` If `.agents/.gitignore` already exists, merge these two lines if they are absent; do not remove unrelated ignore rules. 5. If the repo does not track `.agents/.gitignore` and the user relies on the repo root `.gitignore`, ensure equivalent patterns exist there: `.agents/sessions/*` and `!.agents/sessions/README.md`. Do not create durable knowledge files (`AGENTS.md`, `docs/`, `playbooks/`) as part of this skill; those are owned by `learning-distill` initialization or a full kit merge. ## Output location Write inside the repo to `.agents/sessions//`. The session folder name is a sortable storage label. The canonical task/session identifier is the `task_id` field inside the bundle's `summary.json`. ## Required outputs - summary.json - active-task.md - learning-candidate.md - changed-files.txt - validation.txt ## Example bundle Filled-in reference files live under `.agents/skills/task-closeout/example/task-bundle/` when this skill is installed under `.agents/skills/task-closeout/`. ## Rules - Record only observable facts in active-task.md. - Record only candidate lessons in learning-candidate.md. - Distinguish clearly between what failed, what worked, and what is only a hypothesis. - Do not update `.agents/AGENTS.md` or any other durable repo knowledge file. - Record the associated OpenSpec change, if any, in `summary.json` under `openspec_change` (the change name from `openspec/changes//`). Omit the field when the session touched no OpenSpec change. - Never modify anything under `openspec/` during closeout of an in-flight change; spec updates happen at `/opsx:archive` time, not closeout time. - Do not edit files under `.agents/skills/` during closeout. Capture proposed skill or `MAINTENANCE.md` edits as text in the bundle; **learning-distill** applies kit-wide skill changes. - Treat the **whole maintainer conversation** as in-scope for `active-task.md` and `learning-candidate.md` unless the user explicitly limits closeout to one subtask (mistakes, reversals, and corrections—not only the last `git diff`). - Do not write narrative summaries longer than necessary. - Prefer concise bullet lists. ## Procedure 1. Determine or create `repo_id`. 2. Determine or create `task_id`. 3. Create a session folder using the pattern `YYYYMMDD-HHMMSS-short-topic`. 4. Keep one task-closeout bundle per session folder. 5. Collect changed files. 6. Collect commands run and validation results. 7. Re-read the full session (or transcript) before drafting bundle prose so notes and lessons are not scoped to the final edit only. 8. Write active-task.md. 9. Write learning-candidate.md. 10. Write summary.json with status, metadata, `repo_id`, `task_id`, `openspec_change` (when applicable), and optional agent identifiers when available. 11. Mark the session bundle ready for distillation. ## Optional agent metadata Record agent provenance whenever the active tool can supply it. Record session provenance whenever the active tool can supply a stable session identifier. - In `summary.json`, add `agent` when the active agent/tool identity is known. - In `summary.json`, add `agent_session_id` when the active agent/tool exposes a stable session ID. - In `active-task.md`, add an Agent section when the agent/tool identity is known. - In `active-task.md`, add an Agent Session ID section when the active agent/tool exposes a stable session ID. - Treat `agent` and `agent_session_id` independently: record either one when available; omit only the specific field/section that is unavailable. - Do not invent session IDs or require manual lookup outside the agent/tool's supported session history. ## Session folder naming - Use a deterministic, sortable folder name such as `YYYYMMDD-HHMMSS-short-topic`. - Keep the slug short, lowercase, and tied to the task goal. - Reuse the same session folder only for the single task-closeout bundle it was created for. - Do not treat the folder name as the canonical task identity; use the `task_id` field in `summary.json`. ## active-task.md sections - Task ID - Agent (optional) - Agent Session ID (optional) - Goal - Outcome - Files Changed - Commands Run - Validation - Remaining Work - Notes ## learning-candidate.md sections - Task - What failed - What worked - Reusable pattern - Candidate AGENTS update - Candidate troubleshooting note - Candidate repo decision - Candidate playbook - Spec updates deferred to archive time (change name + what to fold in) - Confidence