# Os Done Or Not

ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or...

- Repository: https://github.com/kharmanskyi/open-steps (1291 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-05
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kharmanskyi/open-steps --skill os-done-or-not -g -a claude-code -y`
Codex: `npx skills add kharmanskyi/open-steps --skill os-done-or-not -g -a codex -y`
Cursor: `npx skills add kharmanskyi/open-steps --skill os-done-or-not -g -a cursor -y`
Gemini CLI: `npx skills add kharmanskyi/open-steps --skill os-done-or-not -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add kharmanskyi/open-steps`

## Description

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 instead of re-exploring the repo.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# os-done-or-not

One question, one screen: **did the agent finish, and what actually happened**,
in words a reader who does not code will understand. Nothing happened (pure
questions, no files touched) → one line saying so, no report.

## Language

The user's language in this session, detected from the conversation. Translate
every template label. Code, files, commands stay English.

## Step 1 - gather proof that takes seconds

Fast checks only; never re-run the test suite - use results this session
already produced. Not confirmable in seconds, or still running → **"not
checked"**, never "yes".

```bash
git status --porcelain            # uncommitted?
git log --oneline -10             # what landed
git log HEAD --not --remotes --oneline 2>/dev/null | head -20   # unpushed? (no remote: say so)
gh pr view --json state,mergeStateStatus && gh pr checks   # if a PR exists
```

## Step 2 - name the outcome

Sessions end one of eight ways; pick the match **before** writing, or the
report says "fully done: yes" and "safe to close: no" in the same breath.

| # | Outcome | Verdict shape |
|---|---|---|
| 1 | Shipped and verified | done Yes · nothing needed · close Yes |
| 2 | Done - one action is yours | done Yes · needed = that action · close Yes |
| 3 | Stalled on your decision | done No · needed = the decision · close No |
| 4 | Partly done, rest deferred | core Yes, rest recorded as debt · close Yes |
| 5 | Didn't work - rolled back | done No · lead = what was learned · close Yes |
| 6 | Something broke | lead opens with ⚠️ · risk in full (rule 7) · close No |
| 7 | Research only | the answer is the result · skip ship rows · close Yes |
| 8 | Nothing to report | one line, no report, no file |

Outcomes 5 and 6 are where reports start lying; "the approach failed and was
rolled back" is a complete result.

## Step 3 - write the report (translate the labels, keep the shape)

```
<Lead: 1, 2 sentences. What changed for the product. Best result first.>

The rest: https://github.com/kharmanskyi/open-steps/blob/HEAD/skills/os-done-or-not/SKILL.md