kharmanskyi/open-steps

What is it?

Key features

• 01Reports finished work as a one-screen verdict covering done status, user actions and new debt.
• 02Gives non-technical users numbered steps and attempts tasks itself before asking.
• 03Checks claims from other sessions against what actually happened.
• 04Rewrites any engineering-heavy text in plain words without losing facts.
• 05Maintains a BIG-PICTURE.md file tracking features, unused code and queued work.
• 06Supports Claude Code, Codex CLI, Cursor CLI and Gemini CLI.

Use cases

• Non-engineers who build products with an AI coding agent and need to know whether work is finished.
• Founders or product managers who want plain status reports instead of commit logs.
• Teams that want a second session to verify another agent's claims before accepting them.
• Deciding whether to proceed with a hard-to-undo change, such as a migration or launch.

Quick start

1. 1

   Clone the repository

   git clone https://github.com/kharmanskyi/open-steps.git
2. 2

   Install the pack as a Claude Code plugin

   claude plugin marketplace add ./open-steps && claude plugin install open-steps@open-steps
3. 3

   Add the routing block to your Claude Code instructions file

   grep -q 'os-done-or-not' ~/.claude/CLAUDE.md 2>/dev/null || cat open-steps/docs/routing-block.md >> ~/.claude/CLAUDE.md

Things to know

• !The README tests only Claude Code in full; the skills on Codex CLI, Cursor CLI and Gemini CLI are untested for permissions.
• !The pack can merge pull requests on its own once checks pass and a review is approved, unless a note on the task says otherwise.
• !Updating requires both a git pull in the clone and a plugin update, otherwise an old copy stays installed.

Topics

FAQ

What is open-steps?

Plain-language agent skills for Claude Code, Codex CLI, Cursor CLI and Gemini CLI that turn session reports into a one-screen verdict anyone can follow. Open Steps is a set of agent skills that change how coding agents report their work. Instead of commit hashes and engineering jargon, the agent gives a short report with a clear verdict: whether the work is done, whether anything is needed from the user, what new technical debt was created, and whether it is safe to close the session.

Is open-steps free to use? What license does it have?

open-steps is open source under the MIT license. Check the license terms before using it in commercial products.

Is open-steps still maintained?

Actively maintained. The last commit to open-steps was on Oct 5, 2026.

What can I use open-steps for?

Non-engineers who build products with an AI coding agent and need to know whether work is finished. Founders or product managers who want plain status reports instead of commit logs. Teams that want a second session to verify another agent's claims before accepting them. Deciding whether to proceed with a hard-to-undo change, such as a migration or launch.

How do I install open-steps?

Clone the repository: git clone https://github.com/kharmanskyi/open-steps.git Install the pack as a Claude Code plugin: claude plugin marketplace add ./open-steps && claude plugin install open-steps@open-steps Add the routing block to your Claude Code instructions file: grep -q 'os-done-or-not' ~/.claude/CLAUDE.md 2>/dev/null || cat open-steps/docs/routing-block.md >> ~/.claude/CLAUDE.md

Where can I get open-steps?

The source code and installation instructions are on GitHub: https://github.com/kharmanskyi/open-steps