plan-eng-review

Review engineering plans and architecture to surface risks and gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often start coding before the plan is locked, leading to architecture mistakes, missed edge cases, fragile tests, and costly rewrites; this Skill acts like an engineering manager to lock the execution plan and surface problems before implementation begins.

Core Features & Use Cases

  • Architecture review: Evaluate system boundaries, data flow, dependencies, and blast radius with concrete recommendations.
  • Test and coverage guidance: Specify required tests, coverage targets, and suggest test harnesses and edge-case checks.
  • Interactive planning: Walk through issues with AskUserQuestion prompts, design-doc checks, ASCII diagrams, and step-by-step remediation.
  • Use Case: Run a pre-implementation review for a new feature branch to catch scalability issues, missing invariants, and deploy/release gaps before the first PR.

Quick Start

Run an interactive engineering review by invoking /plan-eng-review and provide the branch or design doc you want reviewed.

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

To review an engineering plan, evaluate system boundaries, data flow, and blast radius to lock execution details. This surfaces actionable risks and gaps before coding starts, preventing architecture mistakes and costly rewrites.

What is a pre-implementation architecture review and when do I need it?

A pre-implementation architecture review evaluates system dependencies and scalability for a feature branch before coding. You need it before the first PR to catch missing invariants, fragile tests, and deploy gaps early.

How do I specify required tests and coverage targets for a new design doc?

Specify required tests and coverage targets by generating recommendations for test harnesses and edge-case checks during the design doc review. This locks testing requirements before development and prevents coverage gaps.

Can I use interactive prompts to walk through design doc checks and remediation?

Yes, you can use interactive AskUserQuestion prompts to walk through design doc checks step by step. This generates ASCII diagrams and interactive remediation paths to resolve architectural issues.

Does this engineering review process provide rollout strategy and performance recommendations?

Yes, the engineering review process provides rollout strategy and performance recommendations. It evaluates system architecture to generate concrete guidance for deploy releases and performance optimization.

What is the best way to catch scalability issues and missing invariants in a feature plan?

The best way to catch scalability issues and missing invariants is running an engineering manager-style review on the feature plan. This surfaces architectural gaps and generates step-by-step remediation before implementation.