plan-eng-review

Review engineering plans for architecture, data flow, edge cases, and test coverage.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/mi179/claude-skills --skill plan-eng-review-mi179
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/plan-eng-review
Command: npx skills add https://github.com/mi179/claude-skills --skill plan-eng-review-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

Core Features & Use Cases

  • Interactive architecture review with opinionated recommendations to surface risks early.
  • Lock-in of execution plan: data flow, components, edge cases, test coverage, and performance considerations.
  • Guided decision-making when users present plans or design docs, with actionable next steps and tradeoffs.
  • Reusable plan artifacts and diagrams to inform implementation and reviews.

Quick Start

Provide an end-to-end engineering review plan and a ready-to-use execution checklist.

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 starting implementation?

Review an engineering plan by interactively evaluating architecture, data flow, edge cases, and performance gaps. This process surfaces risks early and provides opinionated recommendations to lock in a reproducible execution plan before coding begins.

What is an architecture review and when do I need it?

An architecture review identifies gaps in data flow, components, test coverage, and performance considerations. You need it when you have a design doc ready and want to catch structural issues and surface tradeoffs before starting the implementation phase.

How do I check my design doc for edge cases and test coverage gaps?

Check your design doc through a structured engineering review that assesses data flow and test coverage. This interactive evaluation captures decisions and risk considerations, generating an actionable execution checklist to address missing edge cases.

Can I get actionable recommendations during a technical plan review?

Yes, a technical plan review provides opinionated recommendations by walking through architecture issues interactively. It guides decision-making with actionable next steps and tradeoffs, ensuring your execution plan captures diagrams and risk considerations.

What is the best way to lock in an execution plan for software engineering?

The best way to lock in an execution plan is through a structured engineering review that enforces prompt usage to capture decisions and diagrams. This creates reusable plan artifacts that document performance constraints and edge case handling.