Skip to content
coworkplugins

Claude skill

Os Done or Not

Os Done or Not is a Claude skill in the Open Steps plugin. 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…

CommunityShips in Open StepsDeveloper Tools

What it does

The description in the skill's SKILL.md, which Claude reads to decide when to use it:

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.

The skill's instructions (about 1,199 words) cover:

  • Language
  • Step 1 - gather proof that takes seconds
  • Step 2 - name the outcome
  • Step 3 - write the report (translate the labels, keep the shape)
  • Step 4 - save it
  • Step 5 - fold it into the map
  • Jargon → plain words
  • Hard rules - these rules are the skill
  • Known gotchas

How to use it

  1. Os Done or Not comes inside the Open Steps plugin, so you get it by installing that plugin, along with its 7 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
  2. Ask Claude for the task. When your request matches the skill's description, Claude loads it.
  3. To pick it yourself in Claude chat, type / or click + and choose os-done-or-not. In Claude Code and Cowork, type:
    /open-steps:os-done-or-not

Source

Plugin
Open Steps
SKILL.md
View on GitHub
Repo stars
1,284
Repo last pushed
Nov 15, 2026
Checked
Nov 16, 2026

More skills in Open Steps