plan-eng-review

Reviews implementation plans for architecture, edge cases, and test coverage before coding.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often hide architecture flaws, missing edge cases, and weak test coverage that only surface after code is written. This Skill performs an engineering-manager-style review of a plan or design doc before implementation begins, walking through issues interactively with opinionated recommendations. ## Core Features & Use Cases - Scope Challenge (Step 0): Identifies existing code that already solves sub-problems, flags scope creep, and challenges plans touching 8+ files or 2+ new services. - Architecture & Data Flow Review: Evaluates diagrams, state machines, failure modes, and complexity using engineering leadership heuristics (boring-by-default, blast radius, reversibility). - Test Coverage Analysis: Requires a test diagram and checks whether the plan covers edge cases rather than only the happy path. - Use Case: Before starting a multi-file feature, run this review on your plan to catch an N+1 query risk or a missing rollback path while changes are still cheap. ## Quick Start Ask the assistant to run an engineering review on the current plan or design doc before writing any code.

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?

Run this Skill on your plan or design doc before writing code. It performs a scope challenge, checks architecture and data flow, validates test coverage with a required test diagram, and walks through each issue interactively with recommendations.

What does an engineering plan review check for?

It checks whether existing code already solves sub-problems, flags scope creep and plans touching more than 8 files, evaluates architecture against boring-by-default and blast-radius principles, and verifies edge case and test coverage.

Do I need a design doc before running a plan review?

A design doc is not required but recommended. If none is found, the Skill offers to run the office-hours prerequisite skill first to produce a structured problem statement, then proceeds with a standard review if skipped.

When should I run an architecture review in my workflow?

Run it after a plan or design doc exists but before implementation starts. Catching architecture issues at the plan stage is far cheaper than refactoring after code is written.

Can the review modify my code directly?

No. It is a review-only workflow that presents findings and recommendations interactively. The user decides whether to proceed with each suggested change before any implementation happens.