A command that reviews and improves an implementation plan before coding begins. It checks whether the plan explains the investigation, proposed approach, file-level changes, alternatives, and acceptance criteria, meaning the conditions for considering the work complete.

Use it after writing a plan and before changing code to critique the proposed design, check that the plan is detailed enough, and refine it until the approach is ready for implementation.

It can expose design problems while changes are still inexpensive to alter. Reviewing the plan before implementation helps prevent unclear scope or missing steps from becoming code and rework.

plan-ready — Command for Claude Code by costajohnt/oss-autopilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/costajohnt/oss-autopilot

Made for: Claude Code.

Or install oss-autopilot, the plugin that ships this one along with the rest of its 3 skills, 9 commands, 8 agents, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/costajohnt/oss-autopilot/plan-ready/github.svg)](https://agentmods.dev/commands/costajohnt/oss-autopilot/plan-ready)

Your own site

<a href="https://agentmods.dev/commands/costajohnt/oss-autopilot/plan-ready"><img src="https://agentmods.dev/badge/commands/costajohnt/oss-autopilot/plan-ready/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/costajohnt/oss-autopilot/plan-ready"><img src="https://agentmods.dev/badge/commands/costajohnt/oss-autopilot/plan-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 940 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.00940
Opus 5.5	$0.00012	$0.00376
Sonnet 5.5	$0.00006	$0.00188
Haiku 4.5	$0.00003	$0.00094

Measured 2mo ago against content hash 0a094c2564fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plan-ready scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/plan-ready.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/plan-ready

Drives the plan-review convergence loop that catches design-level problems before any code is written. Mirrors /pr-ready exactly, but applied to a plan artifact instead of a diff (#1249).

When to use

Run after you have completed investigation and written an implementation plan, BEFORE you start implementing. A solid plan caught and refined here is much cheaper than the same problem caught after 200 lines of code exist.

The slash command auto-locates the plan artifact at /tmp/oss-autopilot-plans/<repo>-<issue-number>.md. Pass the path explicitly if the plan lives elsewhere: /plan-ready /tmp/some-plan.md.

What it does

For the named plan artifact:

Verify the plan is complete enough to evaluate. Check that it has sections covering: investigation findings, proposed approach, specific file-level changes, alternative approaches considered, and acceptance criteria. Block readiness if the plan is a stub (single paragraph, no structure) — that needs more drafting before review.
Dispatch the pr-review-toolkit agents in parallel against the plan text:
- pr-review-toolkit:code-reviewer — design-level critique (does the proposed approach make sense for the codebase? Are there simpler / more idiomatic alternatives the plan missed?)
- pr-review-toolkit:silent-failure-hunter — does the plan name how it handles edge cases, error paths, partial failures, or does it silently assume the happy path?
- pr-review-toolkit:code-simplifier — is the plan's scope right? Is there a simpler change that achieves the same outcome?
- devils-advocate — actively try to break the plan. List scenarios where the proposed approach fails or surprises a future reader.
Brief each agent with the plan text, the issue body it targets, and any contributing-guidelines context already discovered.
Triage findings:
- Critical findings (plan is wrong / incomplete in a way that would force a rewrite mid-implementation): block readiness.
- Recommended findings (plan ships but is suboptimal — wrong file structure, missed alternative): block readiness.
- Minor findings (wording, sectioning): report but don't block.
- Out-of-scope findings: list as "deferred to follow-up plan".

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 93 lines · 30 tokens per session scan A 0a094c2564fe

Subscribe to this mod's changes

plan-ready is a command published in the GitHub repository costajohnt/oss-autopilot (26 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 940 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Code review Planning TypeScript cli developer-tools github open-source

plan-ready next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
plan-readycostajohnt/oss-autopilot	Command	26	4d ago	MIT	A	30	Claude Code
review-prscan1357/oh-my-pi	Command	38k	yesterday	MIT	A	0	Claude Code
review-prpablo-albaladejo/kaiord	Command	11	4d ago	MIT	A	7	Claude Code
release-flowcoo1white/cool-workflow	Command	2	2d ago	BSD-2-Clause	A	20	Claude Code
review-branchdamusix/atomic-claude	Command	115	4d ago	MIT	A	35	Claude Code
advanced-code-review-contextaxiomantic/spellbook	Command	11	2d ago	MIT	A	19	Claude Code
mach12:issue-reviewLeanAndMean/scramjet	Command	8	4d ago	Apache-2.0	A	17	Claude Code