plan-eng-review

Review engineering architecture and execution plans for implementation risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents expensive architecture mistakes by forcing a disciplined, engineering-manager style review of an execution plan before implementation starts.

Core Features & Use Cases

  • Architecture and execution-plan locking: Reviews architecture decisions, data flow, diagrams, edge cases, and the intended test coverage so the team can proceed with fewer surprises.
  • Interactive issue-by-issue walkthrough: Guides a discussion through the riskiest parts of the plan with opinionated recommendations aimed at correctness, performance, and maintainability.
  • Proactive plan hardening: Helps when you already have a design doc or plan and you are about to start coding, catching gaps while changes are cheap.

Quick Start

Ask the AI to run an engineering plan review for your architecture and execution steps, including edge cases and test coverage.

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

An engineering plan review evaluates architecture decisions, data flow, and edge cases before implementation. It provides an interactive, issue-focused walkthrough to catch gaps and lock in the execution plan while changes are still cheap.

What is an engineering manager style plan review?

An engineering manager style plan review is a disciplined technical evaluation of a design doc. It examines architecture, diagrams, and test coverage to prevent implementation drift and avoid expensive late-stage rework.

How do I prevent implementation drift from a design doc?

You prevent implementation drift by conducting a thorough plan review that locks in architecture and execution steps. This proactive hardening identifies missing edge cases and performance considerations before development begins.

Can I use this plan review for an existing execution plan?

Yes, this plan review is designed for existing design docs and execution plans. It is most effective when you are about to start coding, guiding an issue-by-issue discussion through the riskiest parts of your planned implementation.

What does an architecture plan review cover?

An architecture plan review covers architecture decisions, data flow, diagrams, edge cases, test coverage, and performance considerations. It delivers opinionated recommendations aimed at correctness and maintainability.

When should I not do a technical plan review?

A technical plan review should be skipped if you have no design doc or execution plan in place. It requires an existing planned implementation to evaluate for gaps, architecture flaws, and missing test coverage.