←Leaderboard/Writing/open-steps
Last commit on October 5, 2026·Created on August 25, 2026

kharmanskyi/open-steps

“Plan and verify software changes in plain language.”
Combined rank
#341
across all skills
In Writing
#12
category rank
Stars
1.3k
+2.5% in last 7d
Forks
112
0.0% in last 7d
Watchers
46
+2.2% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Open-steps provides a set of constraints and protocols that guide AI agents toward brevity and honesty. By replacing verbose AI tendencies with straight verdicts and honest session reports, it helps developers maintain clarity during complex technical tasks.

The collection implements a system of verification and planning, enabling agents to check their own work and identify potential failure points before execution.

WHO IT'S FOR
AI agent power users
standardizing AI communication for clarity and brevity
AI agent / automation builders
implementing structured verification and planning workflows
Technical leads / architects
maintaining high-level project visibility via AI agents
Backend / infrastructure engineers
automating GitHub PR reviews and merge workflows
Categories
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Claude Code plugin

Installs: Open Steps plugin bundle, including its skills and both hooks, with the routing block added separately. The listed skill paths are a bounded selection. · Claude Code

Before you start
  • git must already be installed.
  • gh is optional; some project-state checks report "not checked" without it.

Run from: The directory containing open-steps/ after cloning, not the clone itself.

  1. In a terminal, download the repository. Stay in the directory where you run this command for the following terminal commands.

    git clone https://github.com/kharmanskyi/open-steps.git
  2. In a terminal, register the downloaded marketplace and install the Open Steps plugin.

    claude plugin marketplace add ./open-steps && claude plugin install open-steps@open-steps
  3. In a terminal, add the routing block to ~/.claude/CLAUDE.md using the documented repeatable command.

    grep -q 'os-done-or-not' ~/.claude/CLAUDE.md 2>/dev/null || cat open-steps/docs/routing-block.md >> ~/.claude/CLAUDE.md
  4. In a Claude Code session, run the installation check. It reports what is connected and marks anything it cannot verify as unchecked.

    /open-steps:os-install-check
README.md ↗ · Checked Nov 5, 2026README.ko.md ↗ · Checked Nov 5, 2026

Give it something to do.

Suggested first task

Make a technical report understandable

Uses os-say-simple

  • Paste a technical report, review comment, error message, or other text to simplify.
Use os-say-simple to rewrite the text I paste below in plain language. Lead with the main point, preserve every number, warning, and caveat, and keep unverified claims attributed to the original text.
skills/os-say-simple/SKILL.md ↗ · Checked Nov 5, 2026
Suggested first task

Get a plain-language recommendation

Uses os-ask-simple

  • Describe one technical choice, the problem it should solve, the alternatives, and relevant constraints.
  • Provide available project context or access to relevant code and configuration.
Use os-ask-simple to assess the technical choice I describe below. Explain the trade-offs in plain words, consider doing nothing and a simpler substitute, and end with one marked recommendation. If this is a structural choice, show the six checks and mark anything you cannot verify as not checked.
skills/os-ask-simple/SKILL.md ↗ · Checked Nov 5, 2026
Suggested first task

Find out whether the work is done

Uses os-done-or-not

  • Use after a session that changed files or completed substantive project work.
  • Provide access to the project state and the session's existing verification results.
  • For GitHub pull-request checks, gh is optional; unavailable checks must be reported as not checked.
Use os-done-or-not to report on the work completed in this session in one short screen of plain language. Say whether it is fully done, whether you need anything from me, whether it created new debt, and whether it is safe to close. Give proof for every yes, mark unverified items as not checked, and use existing test results rather than rerunning the test suite.
skills/os-done-or-not/SKILL.md ↗ · Checked Nov 5, 2026README.md ↗ · Checked Nov 5, 2026