plan-eng-review

Name: plan-eng-review
Availability: InStock
Author: a29paul

Review software architecture and execution plans for design flaws and test coverage gaps.

1|Updated Apr 13, 2026

Search Tags:#performance #data flow #engineering plan #test coverage #architecture review #technical review #execution plan

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of shipping code with hidden architectural flaws. It catches issues in architecture, data flow, edge cases, test coverage, and performance before implementation begins, saving weeks of rework.

Core Features & Use Cases

Architecture Review: Evaluates system design, data flow, and component interactions.
Edge Case & Test Coverage Analysis: Identifies missing test scenarios and potential failure modes.
Performance & Tradeoff Evaluation: Reviews performance implications and provides opinionated recommendations on technical tradeoffs.
Use Case: Imagine you have a plan to refactor the authentication system. Use this Skill to review the architecture diagram, validate the data flow between services, and confirm test coverage before writing any code.

Quick Start

Use the plan-eng-review skill to review the architecture and execution plan for the proposed authentication refactor.

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 architecture plan for data flow and design flaws before coding?▼

Reviewing an architecture plan for design flaws involves evaluating system design, validating data flow between components, and analyzing test coverage gaps to catch hidden issues before implementation begins. This process identifies edge cases and performance tradeoffs early.

What is the best way to identify edge cases and test coverage gaps in an execution plan?▼

Identifying edge cases and test coverage gaps in an execution plan requires analyzing potential failure modes and validating test scenarios against the proposed system design. This ensures missing test coverage is flagged and resolved interactively during the plan review phase.

Can I evaluate performance tradeoffs and get technical recommendations during an engineering plan review?▼

Evaluating performance tradeoffs during an engineering plan review provides opinionated technical recommendations on system design choices. This validates performance implications and helps resolve data flow issues interactively before development starts.

When do I need to run an architecture review on my software design?▼

You need to run an architecture review when you have an execution plan ready for implementation. Validating system design, data flow, and component interactions before writing code prevents weeks of rework caused by hidden architectural flaws.

Does this technical review work for refactoring an authentication system?▼

Yes, technical review applies to refactoring an authentication system by validating the architecture diagram, confirming data flow between services, and checking test coverage. This ensures the execution plan is robust before any code is written.