task-closeout

星标9

分支2

更新时间2026年4月22日 23:46

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

Hypercubed

Hypercubed/f-flat-minor

打开 GitHub 仓库查看创作者相关仓库

下载

Task Closeout

Goal

Create a temporary handoff packet for later learning extraction.

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.

Resolve the repo root (the directory that contains .git/ in normal layouts).
Ensure .agents/sessions/ exists.
If .agents/sessions/README.md is missing, create it from bootstrap/sessions/README.md in this skill folder.
Ensure .agents/.gitignore exists. If it is missing, create it with exactly:
```
sessions/*
!sessions/README.md
```
If .agents/.gitignore already exists, merge these two lines if they are absent; do not remove unrelated ignore rules.
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/<session-folder>/.

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.
Do not write narrative summaries longer than necessary.
Prefer concise bullet lists.

Procedure

Determine or create repo_id.
Determine or create task_id.
Create a session folder using the pattern YYYYMMDD-HHMMSS-short-topic.
Keep one task-closeout bundle per session folder.
Collect changed files.
Collect commands run and validation results.
Write active-task.md.
Write learning-candidate.md.
Write summary.json with status, metadata, repo_id, task_id, and optional agent identifiers when available.
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/AGENTS.md update
Candidate troubleshooting note
Candidate repo decision
Candidate playbook
Confidence

同仓库更多 Skills

同仓库

docs-search

Hypercubed/f-flat-minor

Search `.agents/` durable knowledge using a local JSON index generated from markdown sources. Use `index-docs.py` to refresh search data, and optionally run docs-compile when you also want durable section index files regenerated.

2026-05-259

docs-compile

Hypercubed/f-flat-minor

Regenerate optional durable docs indexes and rebuild docs-search cache from local markdown sources. Use after editing `.agents/docs/` (any section), and before maintenance passes that validate index alignment.

2026-04-229

knowledge-lint

Hypercubed/f-flat-minor

Check the `.agents/` knowledge layer for duplication, contradiction, staleness, oversized guidance, broken or stale links, missing index coverage, uncategorized or misplaced knowledge, and consistency between `decisions/` and `troubleshooting/` indexes and their entry files. Use as a periodic maintenance pass.

2026-04-229

learning-distill

Hypercubed/f-flat-minor

Read a completed temporary session bundle from `.agents/sessions/` and distill durable repo knowledge into `.agents/` files. Use only after task-closeout has produced a bundle and when the goal is to separate stable guidance from temporary task notes.

2026-04-229

plans

Hypercubed/f-flat-minor

Use whenever working with maintainer plans under .agents/docs/plans/. Covers reading a plan before implementation, creating or scaffolding a plan, and updating status or body during or after work. Trigger when the user asks to plan, scope deferred work, check what is planned, or record a plan. Also trigger at the start of implementation to see whether a plan already exists.

2026-04-229

write-plan

Hypercubed/f-flat-minor

Scaffold a new maintainer plan under `.agents/docs/plans/<id>.md` with valid YAML frontmatter, collision-checked ids, optional body stub sections (link decisions in a

2026-04-229

name	task-closeout
description	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.

Task Closeout

Goal

Create a temporary handoff packet for later learning extraction.

Skill initialization (before first closeout)

Resolve the repo root (the directory that contains .git/ in normal layouts).
Ensure .agents/sessions/ exists.
If .agents/sessions/README.md is missing, create it from bootstrap/sessions/README.md in this skill folder.
Ensure .agents/.gitignore exists. If it is missing, create it with exactly:
```
sessions/*
!sessions/README.md
```
If .agents/.gitignore already exists, merge these two lines if they are absent; do not remove unrelated ignore rules.
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/<session-folder>/.

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.
Do not write narrative summaries longer than necessary.
Prefer concise bullet lists.

Procedure

Determine or create repo_id.
Determine or create task_id.
Create a session folder using the pattern YYYYMMDD-HHMMSS-short-topic.
Keep one task-closeout bundle per session folder.
Collect changed files.
Collect commands run and validation results.
Write active-task.md.
Write learning-candidate.md.
Write summary.json with status, metadata, repo_id, task_id, and optional agent identifiers when available.
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/AGENTS.md update
Candidate troubleshooting note
Candidate repo decision
Candidate playbook
Confidence