os-done-or-not

ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict - fully done, anything needed from you, new debt, safe to close. Every "yes" names its proof; unverified says "not checked". Saves the report so the next session starts from it inst

Install

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools

• REA 456,474 ★
  Reverse engineer anything from your terminal or agent with one CLI and MCP server.
• ask-matt 323,337 ★
  Ask which skill or flow fits your situation. A router over the skills in this repo.
• chief-of-staff 323,337 ★
  Pursue a long-running goal in a single session by co-ordinating subagents.
• claude-handoff 323,337 ★
  Hand the current conversation off to a fresh background agent that picks up the work immediately.
• grill-me 323,337 ★
  A relentless interview to sharpen a plan or design.