plan-eng-review

Reviews implementation plans across architecture, code quality, tests, and performance with interactive decision gates.

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/abdulazeezoj/monovella-poc --skill plan-eng-review-abdulazeezoj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/abdulazeezoj/monovella-poc/tree/main/.agents/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/abdulazeezoj/monovella-poc --skill plan-eng-review-abdulazeezoj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often ship with hidden architecture flaws, missing test coverage, and performance risks that only surface during implementation. This Skill locks in an execution plan by walking through every issue interactively before coding starts, catching problems while they are still cheap to fix. ## Core Features & Use Cases - Four-section review: Evaluates architecture, code quality, test coverage, and performance, with confidence-scored findings and a pre-emit verification gate that requires quoting the motivating code line. - Interactive decision briefs: Each non-trivial finding is presented one at a time via AskUserQuestion with recommendations, completeness scores, and explicit STOP points before the plan is edited. - Outside voice challenge: Runs an independent second opinion from Codex CLI (or a Claude subagent fallback) and surfaces cross-model disagreements for the user to decide. - Use Case: Before implementing a new billing service, run this Skill on the plan document to get an ASCII test-coverage diagram, a written test plan artifact for QA, and an outside-model critique of the architecture. ## Quick Start Ask the assistant to run an engineering review of your implementation plan or design doc before you start coding.

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 implementation plan before coding?

Invoke the plan-eng-review skill on your plan or design document. It walks through architecture, code quality, tests, and performance sections, presenting each finding as an interactive decision with a recommendation before anything is written into the plan.

What does an engineering plan review check for?

It checks system design and coupling, DRY violations and error handling, branch-level test coverage with an ASCII diagram, and N+1 queries or caching gaps. Every finding carries a confidence score and must quote the motivating code line.

Does the plan review work without the Codex CLI installed?

Yes. The outside-voice step preflights Codex availability and falls back to a Claude subagent when Codex is not installed, not authenticated, or unusable. The fallback is the same model family, so its agreement is weighted accordingly.

Why does the review stop after each finding instead of listing them all?

Each non-trivial finding requires explicit user approval through AskUserQuestion before the plan is edited. This anti-shortcut rule prevents the failure mode where findings are dumped into a plan file without the user deciding on each one.

Can the review generate a test plan for QA?

Yes. After the coverage audit it writes a test plan artifact to the project directory listing affected routes, key interactions, edge cases, and critical paths. Downstream QA skills consume this file as their primary test input.