plan-eng-review

Analyze engineering plans and architecture proposals to surface risks and prioritized recommendations.

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

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.

Core Features & Use Cases

  • Interactive, structured plan reviews covering architecture, data flow, diagrams, edge cases, test coverage, and performance.
  • Opinionated recommendations with explicit tradeoffs to help decisions.
  • Proactively analyzes design docs or plans and surfaces issues before coding, catching architectural problems early.

Quick Start

Provide a structured plan review for the current design and deliver actionable recommendations.

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 analyzing architecture, data flows, and test coverage to surface risks and tradeoffs. This process produces a prioritized list of actionable recommendations and evaluation criteria to guide decisions before coding begins.

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

An architecture design doc review evaluates proposals to surface risks, tradeoffs, and improvements across software projects. You need it when reviewing architecture, data flows, test plans, or design docs to catch structural issues early and lock in the execution plan.

Can I use a plan review to check edge cases and test coverage?

Yes, a plan review checks edge cases and test coverage by interactively walking through architecture, data flow, and performance issues. It delivers opinionated recommendations with explicit tradeoffs to help guide your engineering decisions.

What's the best way to evaluate tradeoffs in a software architecture proposal?

The best way to evaluate tradeoffs is through a structured engineering review that analyzes architecture and data flows. It surfaces risks and provides a prioritized list of actionable improvements and evaluation criteria to guide your decisions.

Does this engineering review work for data flow diagrams and performance analysis?

Yes, this engineering review works for data flow diagrams and performance analysis by interactively examining these elements within your design docs. It identifies architectural issues and delivers opinionated recommendations before implementation starts.