plan-eng-review

Reviews engineering plans interactively across architecture, code quality, tests, and performance.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill plan-eng-review-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/raghavbadhwar/rstack/tree/main/plan-eng-review
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill plan-eng-review-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often contain hidden architecture flaws, missing test coverage, and performance risks that only surface during implementation. This Skill locks in an execution plan by walking through issues interactively with opinionated recommendations before any code is written. ## Core Features & Use Cases - Four-section review: Evaluates architecture, code quality, test coverage, and performance, raising each finding as an individual decision with options and recommendations. - Test coverage mapping: Traces every planned codepath and user flow into an ASCII coverage diagram, then adds missing tests (unit, E2E, or LLM eval) to the plan. - Outside voice challenge: Runs an independent second opinion from another AI model (Codex CLI or a subagent) and presents cross-model disagreements for user decision. - Use Case: Before implementing a new billing service, run this Skill on the design doc to catch a missing idempotency plan, untested error paths, and an N+1 query risk, then lock the corrected plan. ## Quick Start Ask the AI to review the architecture and lock in the implementation plan for your current design doc.

Frequently Asked Questions about plan-eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review an engineering plan before implementation?

Invoke the skill on your plan or design doc and it walks through four review sections: architecture, code quality, tests, and performance. Each finding is presented as an individual decision with options, effort estimates, and a recommendation before anything changes.

How does the skill check test coverage in a plan?

It traces every planned codepath and user flow into an ASCII coverage diagram, marking tested paths, gaps, and E2E or eval candidates. Missing tests are added to the plan as specific requirements, and regressions are flagged as critical.

What is the outside voice review in plan-eng-review?

After the main review, it runs an independent second opinion using the Codex CLI or a Claude subagent to find gaps the first review missed. Disagreements between reviewers are presented to the user, who decides each one explicitly.

Can I skip the interactive questions during plan review?

No, findings require explicit user approval by design so no fix lands in the plan silently. In headless sessions the skill blocks, and in spawned sessions it auto-chooses recommended options and reports decisions.

When should I use plan-eng-review versus a code review?

Use it before implementation starts, when you have a plan or design doc, to catch architecture and coverage issues early. Code review of an actual diff is a separate step handled by a different review skill after code exists.