Skip to content
Skills Library
Management & product · Writing

close-task

/close-task

Closing routine for when an important task ends or before the session finishes. Rewrites docs/STATE.md, appends 5 lines to docs/DECISIONS.md and saves decisions and lessons in the vault. Use it when a block of work is completed, a technical decision is made or the user says they are closing the session.

Licence
MIT
Last repository change
12.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Closing routine for when an important task ends or before the session finishes. Rewrites docs/STATE.md, appends 5 lines to docs/DECISIONS.md and saves decisions and lessons in the vault. Use it when a block of work is completed, a technical decision is made or the user says they are closing the session.

Original author description

Closing routine for when an important task ends or before the session finishes. Rewrites docs/STATE.md, appends 5 lines to docs/DECISIONS.md and saves decisions and lessons in the vault. Use it when a block of work is completed, a technical decision is made or the user says they are closing the session.

How it works

SKILL.md has no level-two headings · 22 lines, 295 words

SKILL.md preview
---
name: close-task
description: Closing routine for when an important task ends or before the session finishes. Rewrites docs/STATE.md, appends 5 lines to docs/DECISIONS.md and saves decisions and lessons in the vault. Use it when a block of work is completed, a technical decision is made or the user says they are closing the session.
---

# Close a task

> **Requirement:** the project must have the `## Memory` block in `AGENTS.md` and the file `docs/STATE.md`. If either is missing, the memory is not set up: use the `iniciar-memoria` skill first (or tell the user) and do not go on.

The vault paths (`<vault>`, `<decisions>`, `<lessons>`, `<index>`) are in the `## Memory` block of `AGENTS.md`. Do these steps in order. If something does not apply, skip it and say so.

1. **Review what changed.** If there is git, look at `git status` and `git diff --stat`. If not, go over the files you touched.
2. **Rewrite `docs/STATE.md`.** Replace its content; do not pile onto it. Include:
   - Where the work stands.
   - The concrete next step.
   - Blockers and open questions.
   - What is **verified** and what is **unverified**. Be honest: if you did not test something, write it down.
   Keep the file at 40 lines or fewer and update `updated:` with today's date.
3. **Append to `docs/DECISIONS.md`** an entry of at most 5 lines if there was a decision: what, why, what changes and a link. If there was no decision, add nothing.
4. **Big decision** (it changes how something is built): create an ADR note in `<decisions>` with the vault's `ADR.md` template and add it to its index.
5. **Reusable lesson** (a mistake that cost time, something that worked): a note in `<lessons>` with the `Lesson.md` template and a line in its index.
6. **Indexes.** If you created notes, link them from `<index>` or from the index of their folder.
7. **Links.** Check that you left no broken links (see the `audit-memory` skill).
8. **Summarize for the user** in three lines what was saved and where.

Do not save secrets or personal data. Do not delete notes without asking.

Versions

The database has no other skills named close-task.

Database snapshot: 13.11.2026 · package version 0723932fd9ee (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 86close
    Use when a unit of work is complete, before the session ends. Appends the log block, rewrites the one-screen resume point, checks raw/, commits and pushes.
  • 86close
    Close out a task or session. Updates handoff, log and decisions, humanizes the prose, then hands the commit to `kstack:commit`. Use when work is done or the session is ending.
  • 100wrap-up
    Close a working session. Writes the daily record (done, learned, next), rewrites the file that says where things stand, and adds the decisions of this session to the decision log. Use when the user says "wrap up", "end the session", "save where we are", or before a risky step as a checkpoint.
  • 90plan-done-closeout
    Close a completed framework/app plan by updating concise plan state, moving plan records to completed, and appending decision history. Use when user says a plan is DONE and asks for closeout.
  • 100sdd-ship
    Archive a completed feature and close the SDD cycle (Phase 4): verify the build is truly complete, archive every phase artifact, capture lessons learned, update all phase documents to Shipped, and clean the working folders. Carries the full ship methodology — verification order,…
  • 100sdd-ship
    Archive a completed feature and close the SDD cycle (Phase 4): verify the build is truly complete, archive every phase artifact, capture lessons learned, update all phase documents to Shipped, and clean the working folders. Carries the full ship methodology — verification order,…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.