agentleFS
Sign inStart free
ayleeaylee/agent-os/.agents/skills/closeout/SKILL.md

closeout

Skill0 starsChanged 4 months agoMITView on GitHub

Close or park an explicit unit of work when the user invokes closeout. Use for deliberate state reconciliation, verification, receipts, and an optional handoff; never infer it from casual phrases such as “done” or “thanks.”

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prototype, teach and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

    Also in 4 projects that use this

  • GoogleSkill

    teach

    Teach the user a new skill or concept, within this workspace.

    Also in 3 projects that use this

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 3 projects that use this

  • +4 more from google

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat closeout as a previewed transaction with independent effect boundaries.

    line 8
  2. Very specific:

    Read the owner binder, linked WORKSTREAM.md, relevant artifacts, and verification evidence.

    line 12
  3. Distinctive:

    Ask before any optional effect not already authorized by the user’s request.

    line 20
  4. Very specific:

    Update the workstream to concise current truth and verification.

    line 24
  5. Distinctive:

    Create a uniquely named lifecycle receipt.

    line 25
  6. Very specific:

    Do not create a handoff unless a real agent, runtime, machine, parallel-lane, or context boundary exists.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Close out

Treat closeout as a previewed transaction with independent effect boundaries.

Preview

Read the owner binder, linked WORKSTREAM.md, relevant artifacts, and verification evidence. Present:

  • outcome: shipped, completed locally, parked, or blocked;
  • snapshot changes needed;
  • receipt to create;
  • unresolved risks or missing verification;
  • optional effects: Git, PR, publishing, archive/tombstone, cross-repo memory, or handoff.

Ask before any optional effect not already authorized by the user’s request.

Apply

  1. Update the workstream to concise current truth and verification. Leave exactly one next action while active, parked, or blocked. Set status: closed only when nothing required remains, and use None — closed. as the exact terminal sentinel.
  2. Create a uniquely named lifecycle receipt. Never append to a shared log.
  3. Do not create a handoff unless a real agent, runtime, machine, parallel-lane, or context boundary exists. If one exists, suggest $handoff.
  4. Give a human recap: outcome, what changed, evidence, remaining risk, and next action.

Git is optional evidence, not the state system. Never delete artifacts because Git might retain them, and never create a repository-local archive that conflicts with nearer policy.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free