Verified:GitHub

plan-eng-review

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

6|2|Updated Oct 18, 2021

Search Tags:#architecture #performance #data flow #execution planning #test coverage #engineering review #design diagrams

Ready to run

npx skills add https://github.com/jerrywu001/jerrywu001 --skill plan-eng-review-jerrywu001

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/jerrywu001/jerrywu001/tree/main/.claude/skills/plan-eng-review
Command: npx skills add https://github.com/jerrywu001/jerrywu001 --skill plan-eng-review-jerrywu001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents costly rework by reviewing an engineering plan like an engineering manager in “lock in the execution plan” mode, focusing on architecture, data flow, edge cases, test coverage, and performance tradeoffs before implementation starts.

Core Features & Use Cases

Architecture & execution plan review: validates system design, component boundaries, and dependency/coupling risks to reduce blast radius surprises.
Interactive issue walkthrough with recommendations: guides you through gaps in data flow, diagrams, and sequencing with opinionated, actionable fixes.
Engineering readiness checklist: forces consideration of edge cases, test coverage, and performance so the team can implement with confidence.

Quick Start

Ask for a plan review by saying: "Review my architecture plan for correctness and completeness, then help me lock in the execution plan with diagrams, edge cases, test coverage, and performance considerations."

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 my architecture plan for correctness before starting implementation?▼

Architecture plan review validates system design, component boundaries, and dependency risks to reduce blast radius. It locks in data flow, diagrams, edge cases, test coverage, and performance tradeoffs before coding begins.

What should an engineering execution plan include to prevent costly rework?▼

An engineering execution plan should include architecture diagrams, data flow mapping, edge case handling, test coverage strategy, and performance tradeoffs. Reviewing these elements beforehand prevents rework by identifying gaps early.

How do I identify edge cases and coupling risks in my system design?▼

Identify edge cases and coupling risks through interactive plan walkthroughs that validate component boundaries and dependency mapping. Opinionated analysis exposes sequencing gaps and provides actionable fixes for engineering readiness.

When do I need to lock in an execution plan with test coverage and performance considerations?▼

Lock in an execution plan when you have a design doc and are about to start implementation. Forcing consideration of test coverage and performance at this stage ensures the team can implement with confidence.

Can I get actionable recommendations for gaps in my engineering design diagrams?▼

Yes, interactive issue walkthroughs provide opinionated recommendations for gaps in engineering design diagrams. The review guides you through missing data flow and sequencing with clear, actionable fixes and explicit next-step guidance.

What is the best way to validate component boundaries and blast radius in an architecture plan?▼

The best way to validate component boundaries is through an engineering readiness checklist that reviews architecture and dependency coupling risks. This reduces blast radius surprises by locking in execution plans before coding.