plan-eng-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng manager-mode plan review helps engineering leaders lock in an execution plan for complex software initiatives by surfacing architecture, data flow, edge cases, test coverage, and performance considerations early in the process.

Core Features & Use Cases

  • Interactive plan-review workflow that walks through architecture diagrams, data flow, risk factors, and trade-offs with opinionated recommendations.
  • Use when asked to "review the architecture", "engineering review", or "lock in the plan" to align stakeholders and prevent scope creep.
  • Proactively surface issues when a design doc exists and coding is about to start, catching problems before implementation.

Quick Start

Provide your design doc and ask plan-eng-review to walk through architecture, data flow, edge cases, test coverage, and performance.

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 to lock in architecture before coding?

To review an engineering plan, provide your design doc and analyze architecture, data flow, edge cases, test coverage, and performance to surface issues early. This structured evaluation delivers opinionated recommendations to align stakeholders before implementation begins.

What is an engineering plan review and when do I need one?

An engineering plan review is a structured evaluation of architecture, data flow, and risk factors. You need one when a design doc exists and coding is about to start, ensuring stakeholders align and scope creep is prevented before implementation.

How do I assess test coverage and edge cases during a design doc review?

Assess test coverage and edge cases by walking through an interactive workflow that evaluates architecture diagrams, data flow, and performance trade-offs. This process guides coverage with structured steps, diagrams, and risk assessments to propose concrete improvements.

Can I use this plan review workflow to prevent scope creep on complex software initiatives?

Yes, you can use this plan review workflow to prevent scope creep by proactively surfacing architecture and performance issues. It helps engineering leaders lock in an execution plan by providing opinionated recommendations based on design-doc context.

What's the best way to align stakeholders on architecture trade-offs and risk factors?

The best way to align stakeholders is to walk through architecture diagrams, data flow, and risk factors with opinionated recommendations. This interactive review process evaluates trade-offs and proactively surfaces issues to lock in the execution plan.