plan-eng-review

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill plan-eng-review-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/plan-eng-review
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill plan-eng-review-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering plans often have hidden architecture gaps, edge case oversights, or test coverage holes that only become obvious after hours of coding, leading to costly rework and delayed launches. This skill acts as an engineering manager to catch these issues before you write a single line of implementation code.

Core Features & Use Cases

  • Interactive Plan Review: Walks through your architecture, data flow, diagrams, edge cases, test coverage, and performance considerations with opinionated, actionable recommendations.
  • Proactive Triggering: Automatically suggests a review when you have a plan or design doc ready to start coding, so you never miss a critical pre-implementation check.
  • Use Case: You just finished a design doc for a new payment processing feature. Run this skill to validate the architecture, confirm test coverage for failure scenarios like network timeouts, and lock in an executable plan before your team starts building.

Quick Start

Use the plan-eng-review skill to review the attached architecture plan for the new user onboarding flow.

Frequently Asked Questions about plan-eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an engineering plan review and why do I need it before coding?

An engineering plan review validates architecture design, data flow, and edge case handling before implementation to eliminate costly post-coding rework. It proactively catches hidden architecture gaps and test coverage holes early, ensuring your execution plan is executable and low-risk.

How do I review a technical design doc to catch architecture flaws?

To review a technical design doc, you walk through architecture, data flow, edge cases, test coverage, and performance tradeoffs interactively. This skill delivers opinionated, engineering manager-style recommendations to lock in executable, low-risk execution plans.

Can I use this skill to validate test coverage and edge case handling for a new feature?

Yes, you can use this skill to validate test coverage planning and edge case handling for new features. It reviews failure scenarios like network timeouts within your design doc, confirming your architecture handles these critical pre-implementation checks before development.

What's the best way to analyze performance tradeoffs in a pre-implementation plan?

The best way to analyze performance tradeoffs is through an interactive plan review that evaluates your architecture design and data flow logic. This process delivers actionable recommendations to confirm performance considerations are locked in before coding begins.

Does this plan review work for any software project architecture design?

Yes, this plan review applies to pre-development engineering plan reviews for any software project. It covers architecture design, data flow logic, edge case handling, test coverage planning, and performance tradeoff analysis regardless of your specific tech stack.

When should I avoid using an automated architecture review for my design doc?

You should not use an automated architecture review if you lack a finalized design doc or pre-implementation plan. This skill requires an existing architecture plan to evaluate data flow and edge cases, as it cannot generate initial designs from scratch.