A checklist and procedure for reviewing software implementation plans. It examines whether the work is complete, appropriately simple, testable, and divided into sensible steps.

Use it to review plans in a project folder, check their tests and risks, consider existing decisions, and suggest simpler or better-sized implementation steps.

It helps find missing requirements, unnecessary complexity, risky dependencies, and steps that combine unrelated changes before coding begins.

How MarcusJellinghaus/mcp-tools-sql configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to MarcusJellinghaus/mcp-tools-sql. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/MarcusJellinghaus/mcp-tools-sql/main/.claude/skills/plan_review/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/MarcusJellinghaus/mcp-tools-sql

Made for: Claude Code.

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/marcusjellinghaus/mcp-tools-sql/plan_review/github.svg)](https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/plan_review)

Your own site

<a href="https://agentmods.dev/skills/marcusjellinghaus/mcp-tools-sql/plan_review"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/plan_review/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/marcusjellinghaus/mcp-tools-sql/plan_review"><img src="https://agentmods.dev/badge/skills/marcusjellinghaus/mcp-tools-sql/plan_review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 340 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 100% copy Near-identical to another mod 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.00010	$0.00340
Opus 5.5	$0.00004	$0.00136
Sonnet 5.5	$0.00002	$0.00068
Haiku 4.5	$0.00001	$0.00034

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

Security

Grade A, and why

plan_review 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 1mo 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.

Origin

This is a copy

100% identical to plan_review — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/plan_review/SKILL.md · 41 lines

What it actually says

Review Implementation Plan

First, ensure we're up to date: Call mcp__mcp-workspace__git with command "fetch" and args ["origin"]. Use mcp__mcp-workspace__git with command "status" to check working directory state.

Confirm and display the current feature branch name.

Then review the plan:

Please review the project plan for a new feature in folder pr_info/steps. Please revise the project plan with a balanced level of detail. Please let me know if any complexity could be reduced. Please let me know any questions / comments or suggestions you might have.

Please consider the already discussed and decided decisions (if any) under decisions. We do not need to challenge them again unless absolutely necessary.

Focus on:

Completeness of implementation steps
Appropriate level of detail
Opportunities for simplification (KISS principle)
Test coverage strategy
Step granularity — each step should produce exactly one commit. Flag steps with multiple independent parts (A, B, C) that should be split.
Potential risks or blockers
Requirement changes — flag new dependencies (pyproject.toml) that should be applied during planning, not deferred to implementation

For planning standards, see .claude/knowledge_base/planning_principles.md.

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.

1mo ago First seen · 41 lines · 10 tokens per session scan A 1f3754eba2fc

Subscribe to this mod's changes

plan_review is a skill published in the GitHub repository MarcusJellinghaus/mcp-tools-sql (2 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 340 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to plan_review, differing in 3 lines, and is treated as a copy.

Planning

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

mcp-tools-sql: Skill for Claude Code