plan-eng-review

plan-eng-review is a command for Claude Code from ShaheerKhawaja/ProductionOS. It costs 30 tokens per session (529 once invoked), scanned A, original, MIT.

An engineering architecture review command that turns a proposed change into a detailed execution plan. It examines components, data movement, failures, tests, performance limits, and dependencies.

In plain words
What is it for?
Use it to document system architecture, trace normal and empty inputs, map error handling, build a test matrix, define performance targets, and review dependencies.
Why use it?
It exposes missing cases and risky assumptions before implementation begins.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

Part of the productionos plugin — 4 skills, 41 commands, 11 agents shipped together

Good fit Use it to document system architecture, trace normal and empty inputs, map error handling, build a test matrix, define performance targets, and review dependencies.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/shaheerkhawaja/productionos/plan-eng-review
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/ShaheerKhawaja/ProductionOS

Made for: Claude Code.

Or install productionos, the plugin that ships this one along with the rest of its 4 skills, 41 commands, 11 agents.

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.

agentmods badge for plan-eng-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/plan-eng-review/github.svg)](https://agentmods.dev/commands/shaheerkhawaja/productionos/plan-eng-review)
Your own site
<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/plan-eng-review"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/plan-eng-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.

agentmods 80×15 button for plan-eng-review

Your own site · 80×15
<a href="https://agentmods.dev/commands/shaheerkhawaja/productionos/plan-eng-review"><img src="https://agentmods.dev/badge/commands/shaheerkhawaja/productionos/plan-eng-review.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 529 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.00529
Opus 5 $0.00015 $0.00264
Sonnet 5 $0.00006 $0.00106
Haiku 4.5 $0.00003 $0.00053

Measured 12d ago against content hash 12739f68c5e4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

plan-eng-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 12d 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.

.claude/commands/plan-eng-review.md · 70 lines

How it starts

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

/plan-eng-review — Engineering Architecture Review

You are a principal engineer locking in the execution plan. Architecture, data flow, edge cases, test coverage.

Step 0: Preamble

Run templates/PREAMBLE.md. Read target codebase. Identify tech stack.

Step 1: Restate the Execution Target

Summarize the system or plan under review, the intended behavior, and the integration boundaries before diving into architecture.

Review Dimensions

1. Architecture Diagram

Produce an ASCII diagram of the system. Components, data flow, external dependencies.

[Client] → [API] → [Service] → [DB]
                  → [Queue] → [Worker]

2. Data Flow Analysis

For every new data path, trace:

  • Happy path: input → transform → output
  • Nil/empty input: what happens?
  • Upstream error: what happens?
  • Concurrent access: race conditions?

3. Error Path Mapping

For every error that can occur:

Error Trigger Detection Recovery User Sees Tested?

4. Test Matrix

Component Unit Integration E2E Edge Cases Coverage

5. Performance Budget

  • Response time targets (p50, p95, p99)
  • Memory budget per request
  • Database query budget (max N queries per endpoint)
  • Bundle size budget (if frontend)

6. Dependency Analysis

  • New dependencies: justified? Maintained? License compatible?
  • Existing dependency upgrades needed?
  • Breaking changes in transitive deps?

7. Migration Plan

If modifying existing systems:

  • Can this be deployed with zero downtime?
  • Rollback strategy?
  • Feature flag needed?
  • Data migration steps?

Agent References

  • Dispatch architecture-designer for structural analysis
  • Dispatch database-auditor for schema review
  • Dispatch vulnerability-explorer for security paths

Self-Eval

Run templates/SELF-EVAL-PROTOCOL.md. Score: Was every error path traced? Every data flow mapped? Every dependency justified?

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

  1. 12d ago First seen · 70 lines · 30 tokens per session scan A 12739f68c5e4

Subscribe to this mod's changes

plan-eng-review is a command published in the GitHub repository ShaheerKhawaja/ProductionOS (8 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 529 once invoked, about $0.0002 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-08-31.