A review of an implementation plan, which lays out how a software change will be built and delivered. It checks the work needed, technical feasibility, dependencies, risks, timing, and how the change could be reversed.

Auditing feature plans against specifications and checking their rollout and rollback approach.

It reveals omitted tasks, unrealistic schedules, hidden dependencies, and delivery risks before implementation begins.

review-plan — Skill for Claude Code and Codex by tomzx

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.

Any agent

npx skills add tomzx/agents --skill review-plan

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code, Codex.

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/skills/tomzx/agents/review-plan/github.svg)](https://agentmods.dev/skills/tomzx/agents/review-plan)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/review-plan"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-plan/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/skills/tomzx/agents/review-plan"><img src="https://agentmods.dev/badge/skills/tomzx/agents/review-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,269 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.00019	$0.01269
Opus 5	$0.00010	$0.00634
Sonnet 5	$0.00004	$0.00254
Haiku 4.5	$0.00002	$0.00127

Measured 6d ago against content hash 08b66c165f4f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

review-plan 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 6d 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.

skills/review-plan/SKILL.md · 123 lines

How it starts

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

Review Plan

Audits an implementation plan and reports findings across six categories: completeness, feasibility, dependencies, risk coverage, timeline realism, and reversibility.

Prerequisites

Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
If no argument is provided, locate the feature directory under .sdlc/features/ whose frontmatter issue field references $ISSUE_NUMBER.
.sdlc/features/N-<slug>/plan.md (unified) or .sdlc/features/N-<slug>/plan/index.md plus its sibling plan/<concern>.md files (split), or an implementation plan provided in context or as a file path
.sdlc/features/N-<slug>/specification.md (optional, improves coverage analysis)

Steps

Resolve the plan. Look for .sdlc/features/N-<slug>/plan.md first; if absent, look for .sdlc/features/N-<slug>/plan/index.md and read it together with every plan/<concern>.md it lists. Otherwise read from context or as a file path. Treat the whole plan set (index + concern files) as the unit under review.
Cross-reference against the specification or requirements if available.
Run the deterministic checker best-effort: render each mermaid block with mmdc (or npx -y @mermaid-js/mermaid-cli) when available. A tool that is not installed is skipped (never blocks); a render failure is a blocking finding under Dependencies or Timeline Realism.
Identify issues in each category below. For a split plan, also check that plan/index.md aggregates milestones, cross-concern dependencies, risks, and timeline consistently with the concern files.
Report findings. Omit any category that has no findings.
Write the findings to .sdlc/features/N-<slug>/review-plan.md with frontmatter artifact: plan, verdict (approved if there are no blocking findings, changes-requested if the author must address findings, rejected for a fundamental flaw), and reviewed_at: <ISO date>, and the findings as the body, per skills/sdlc/references/shared.md. Record any unresolved open questions in the findings body. For any question that carries meaningful risk to the implementation, also invoke /create-assumption to record it formally.

Read the full file on GitHub · 123 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.

6d ago First seen · 123 lines · 19 tokens per session scan A 08b66c165f4f

Subscribe to this mod's changes

review-plan is a skill published in the GitHub repository tomzx/agents (6 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 1,269 once invoked, about $0.0001 per session on Opus 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-09-03.

Planning Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens