plan-eng-review

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

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill plan-eng-review-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/adamtpang/summon.company/tree/main/.claude/skills/plan-eng-review
Command: npx skills add https://github.com/adamtpang/summon.company --skill plan-eng-review-adamtpang

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 Audit: Traces every codepath and user flow in the plan, produces an ASCII coverage diagram, and adds missing unit, E2E, and eval 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 starting a multi-day feature build, run this Skill on your design doc to catch a missing database index, an untested error path, and an over-engineered component — each resolved interactively before implementation begins. ## 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.

What does the test coverage review check?

It traces every codepath and user flow in the plan, maps branches and error states, then produces an ASCII coverage diagram showing tested paths and gaps. Missing unit, E2E, and LLM eval tests are added to the plan as requirements.

Does the plan 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 the independent second opinion. The review can also be fully disabled via the codex_reviews config setting.

Can the review run non-interactively in headless sessions?

In headless sessions where questions cannot be asked, the review blocks rather than auto-deciding. In spawned orchestrator sessions it auto-chooses recommended options and reports decisions in a completion summary.

When should I not use an interactive plan review?

Skip it for trivial changes with no architecture impact, since every finding requires an explicit user decision. It is designed for plans where catching design flaws early saves significant implementation rework.