plan-eng-review

Reviews engineering plans across architecture, code quality, tests, and performance with interactive findings.

Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aicodepro/ai-agent-nexi --skill plan-eng-review-aicodepro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/aicodepro/ai-agent-nexi/tree/main/agent/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/aicodepro/ai-agent-nexi --skill plan-eng-review-aicodepro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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 before coding begins, catching design problems early. ## Core Features & Use Cases - Four-Section Review: Evaluates architecture, code quality, test coverage, and performance, raising each finding as an individual decision with recommendations and confidence scores. - Test Coverage Audit: Traces every planned codepath and user flow, produces an ASCII coverage diagram, and adds missing unit, E2E, and regression tests to the plan. - Outside Voice Challenge: Runs an independent second opinion from another AI model (Codex CLI or a Claude subagent) and presents cross-model disagreements for user decision. - Use Case: Before implementing a new billing service, run an engineering review on the design doc to catch a missing idempotency plan, untested error paths, and an N+1 query risk, then lock in the corrected plan. ## Quick Start Ask the assistant to run an engineering review of the current plan or design document before starting implementation.

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 coding?

Invoke the plan engineering review on your plan or design document. It walks through architecture, code quality, tests, and performance section by section, presenting each issue as an individual decision with a recommendation before anything is written into the plan.

What does the test coverage review check?

It traces every planned codepath and user flow, maps branches and error states, and compares them against existing tests. Gaps are added to the plan as unit, E2E, or eval test requirements, and regressions are flagged as critical.

Does the review work without the Codex CLI installed?

Yes. If Codex is not installed or not authenticated, the outside-voice step falls back to a Claude subagent for an independent second opinion. The review can also be fully disabled via the codex_reviews config setting.

Can findings be applied to the plan automatically?

No. Every finding requires explicit user approval through an interactive decision prompt before it lands in the plan. Outside-voice recommendations are informational only and never auto-applied.

When should I use plan review versus code review?

Use plan review before implementation starts, when you have a plan or design doc and want to catch architecture and coverage issues early. Use code review after a diff exists to inspect the actual changes.