{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "kharmanskyi-open-steps--get-a-one-screen-done-or-not-report",
 "repo": "kharmanskyi/open-steps",
 "repo_url": "https://github.com/kharmanskyi/open-steps",
 "repo_slug": "kharmanskyi-open-steps",
 "title": "Get a one-screen done-or-not report after each session",
 "page_title": "How to get a one-screen done-or-not report after each session with Open Steps",
 "summary": "Ask \"are we done?\" and get a verdict on done, needed input, new debt and whether it is safe to close.",
 "who": "A founder or product owner building with an AI agent who cannot tell from commit hashes whether a task is finished.",
 "problem": "Agent reports are written in commit hashes and jargon, so the person directing the work cannot judge whether it is done or what they still owe.",
 "outcome": "A short report with a verdict row, a row for anything needed from you, a row for new debt, and a row for whether it is safe to close.",
 "steps": [
  "Run `git clone https://github.com/kharmanskyi/open-steps.git`",
  "Run `claude plugin marketplace add ./open-steps && claude plugin install open-steps@open-steps` (Claude Code)",
  "Run `grep -q 'os-done-or-not' ~/.claude/CLAUDE.md 2>/dev/null || cat open-steps/docs/routing-block.md >> ~/.claude/CLAUDE.md` to add the routing block",
  "Finish a unit of agent work and ask the agent \"are we done?\"",
  "Read the verdict row first, then the row for anything needed from you"
 ],
 "agent_prompt": "In the open-steps repo at <repo-path>, use the os-done-or-not skill to report on the work just finished for <task-name>. Expected output: a one-screen report with a Fully done row, an Anything needed from you row, a New debt row and a Safe to close row. Verify that each row states a verdict and does not rely on commit hashes alone.",
 "agents": [
  "claude-code",
  "codex",
  "cursor",
  "gemini-cli"
 ],
 "difficulty": "Intermediate",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "The routing block must be added by hand on every tool, because the agent decides by itself whether to use a skill and the block is what tells it when.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "shell",
 "requirements": [
  "git, to download and update the pack",
  "One of Claude Code, Codex CLI, Cursor CLI or Gemini CLI installed",
  "gh, GitHub's command-line tool (optional; without it some output says \"not checked\")"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": true,
 "score": 1.0,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/kharmanskyi-open-steps/get-a-one-screen-done-or-not-report/",
 "md": "https://dedupedai.com/use-cases/kharmanskyi-open-steps/get-a-one-screen-done-or-not-report/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/kharmanskyi-open-steps--get-a-one-screen-done-or-not-report.json",
 "api_version": "v1"
}