plan-eng-review

Automate engineering-management plan reviews of architecture, data flow, edge cases, test coverage, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng manager-mode plan review helps leadership lock in execution details for architecture, data flow, diagrams, edge cases, test coverage, and performance, reducing downstream ambiguity.

Core Features & Use Cases

  • Interactive walkthrough of architecture decisions, data flows, and tradeoffs.
  • Proactive recommendations when a design doc exists or a plan is about to be implemented.
  • Clear, concrete next steps and acceptance criteria for engineers.

Quick Start

Ask me to run plan-eng-review when you need to lock in the architecture and execution plan.

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 software architecture and execution plans before coding begins?

Architecture review locks in execution details for data flow, edge cases, test coverage, and performance, reducing downstream ambiguity. An interactive walkthrough provides proactive recommendations and concrete next steps with acceptance criteria for engineers.

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

An engineering plan review is a management process that validates architecture decisions, data flows, and tradeoffs before implementation. You need one when a design doc exists or a plan is about to be coded and you want proactive recommendations.

How do I identify edge cases and test coverage gaps in my architecture design?

Edge cases and test coverage gaps are identified through an interactive, diagram-supported walkthrough of architecture decisions and data flows. This process highlights tradeoffs and produces concrete next steps and acceptance criteria to resolve missing coverage.

Can I get proactive recommendations on data flow and performance tradeoffs during a plan review?

Proactive recommendations on data flow and performance tradeoffs are generated during the engineering review process. The interactive walkthrough surfaces issues and provides actionable next steps ready to execute as you begin coding.

What's the best way to lock in architecture decisions and reduce downstream ambiguity?

The best way to lock in architecture decisions is running an engineering-management plan review that validates data flow, edge cases, test coverage, and performance. This produces clear acceptance criteria and concrete next steps for the engineering team.

Do I need an existing design doc to run an architecture and execution plan review?

An existing design doc is not strictly required, but the review applies most effectively when a design doc exists or a plan is about to be implemented. This context enables proactive recommendations and concrete next steps during the walkthrough.