closeout

Drive tasks to verified closeout with zero open items and relay handoffs.

Updated May 31, 2026
One-click install
npx skills add https://github.com/4444J99/limen --skill closeout-4444j99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closeout
Source: https://github.com/4444J99/limen/tree/main/.agents/skills/closeout
Command: npx skills add https://github.com/4444J99/limen --skill closeout-4444j99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-repo and multi-agent work often ends with dangling items, uncommitted changes, and unclear ownership of remaining tasks. This Skill enforces a rigorous closeout process so nothing is left open, unverified, or undocumented. ## Core Features & Use Cases - Ground-Truth Verification: Fan out parallel read-only explorers across every repo, component, and ledger, merging structured findings into one conflict-flagged report. - Idempotent Fixed Point: Re-run the done-predicate (such as scripts/verify-whole.sh) until it produces zero changes, proving the work is truly finished. - Clean Commits and Handoff: Commit all loose work explicitly per path, confirm clean git status everywhere, and produce a continuation capsule plus a concise relay handoff note. - Use Case: After a cross-repo feature lands, use this Skill to verify every owner's ledger, close residual gaps in their owning systems, and hand off a tested launch command for the next session. ## Quick Start Ask the agent to close out the current task and produce a relay handoff with zero open items.

Frequently Asked Questions about closeout

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

FAQPage Schema
How do I close out a task with no open items?

Verify ground truth read-only across all owners, close every gap in its owning repo or ledger, re-run the done-predicate until it produces no changes, commit all loose work, and produce a relay handoff. Closeout is only declared when zero items remain open.

What is an idempotent fixed point in task verification?

An idempotent fixed point means re-running the verification predicate, such as scripts/verify-whole.sh, produces no changes and exits 0. If a re-run still mutates state, the work is not done and gaps must be closed first.

How should residual work be recorded during closeout?

Each open item must be resolved immediately or recorded in its own owner's record, the repo or ledger that owns it, with the cheapest path to resolution. Nothing is parked in a throwaway list outside its owner.

Can I use git add -A when committing closeout work?

No. The Skill requires adding paths explicitly with git add <path>, never -A, then committing and confirming git status is clean in every repo touched. Merges and deploys are left to the human owner.

What is a continuation capsule in a handoff?

A continuation capsule is an isolated next-session worktree or owner-native workspace containing a README prompt index, intent/runtime/closeout modules, executable completion predicates, one launch command, and a durable owner receipt.