finishlisted

Drive the current task to fully delivered — recover the goal, finish what remains, verify end-to-end, docs, commit, PR, release checklist, close the ticket. Never stops at a recap, blocker, or partial handoff. Triggers on: /finish, 'finish this', 'drive it to done', 'ship it', 'don't stop at a recap', 'see it through'.
phnx-labs/.agents · ★ 0 · Code & Development · score 62

Install: claude install-skill phnx-labs/.agents

# sessions:finish — drive the current task to delivered You are finishing the current task. Context: $ARGUMENTS This is not a recap. It is an execution contract: recover the goal, finish what remains, verify the real flow, and ship. If the current task is genuinely already delivered (e.g. `/continue` just drove it there), say so **with evidence** and stop there. > **`/finish` vs the neighbors.** For draining a whole *queue* of tickets/branches to > merged, that's `/code:loop` (engineering) or `/work:loop` (any kind). To *recap and > exit* the session, that's `/recap` then `/self:close`. `/finish` is the anti-stopping > driver for the one task in front of you. ## 1 — Recover the contract Re-read the conversation from the start and write a short checklist: - **Original ask** — what the user asked you to deliver. - **Scope changes** — follow-up requests or constraints added later. - **Commitments** — actions you said you would take. - **Current state** — what is done, in progress, or not started. Every item gets a verdict: DONE, IN FLIGHT, NOT STARTED, or BLOCKED. Do not trust memory — back each DONE or BLOCKED with fresh evidence: file:line, command output, test result, PR/deploy URL, HTTP response, ticket state, or the exact error. If you can't quote it, it is not DONE. ## 2 — Convert status into the next action For every IN FLIGHT / NOT STARTED / BLOCKED item, pick the next executable action. Before you call anything blocked, make three distinct attempts and quote ea