plan-eng-review

Guide engineering plan reviews with architecture, data flow, and tradeoff recommendations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations.

Core Features & Use Cases

  • Priority-driven plan evaluation with explicit tradeoffs and recommendations.
  • ASCII diagrams and structured walkthroughs of architecture, data flow, and edge cases.
  • Interactive guidance to align teams on plan direction and next steps.

Quick Start

Initiate a plan-eng-review session to lock in the execution plan and gather actionable recommendations.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
How do I conduct an engineering plan review to lock in architecture and data flow?

An engineering plan review evaluates execution plans by walking through architecture, data flow, edge cases, and test coverage interactively. It generates actionable recommendations, ASCII diagrams, and explicit tradeoffs to align teams on the execution direction.

What is the best way to document architecture tradeoffs and edge cases during a design session?

Documenting architecture tradeoffs during a design session involves structured walkthroughs that evaluate edge cases and performance criteria. This process generates documented tradeoffs and clear next steps, ensuring team alignment on the engineering plan.

Can I use ASCII diagrams to visualize data flow and architecture during a plan review?

ASCII diagrams are fully supported to visualize data flow and architecture during a plan review. They are used within structured walkthroughs to evaluate edge cases and document tradeoffs, providing clear visual guidance for engineering teams.

Does plan review guidance include recommendations for test coverage and performance criteria?

Plan review guidance explicitly includes recommendations for test coverage and performance criteria. It evaluates execution plans based on priority, ensuring these criteria are locked in alongside architecture and data flow before moving forward.

How do I structure an interactive engineering plan evaluation with actionable recommendations?

To structure an interactive engineering plan evaluation, guide teams through priority-driven assessments of architecture and edge cases. This yields explicit tradeoffs, opinionated recommendations, and clear next steps to finalize the execution plan.

When do I need a structured plan review for architecture decisions?

A structured plan review is needed during engineering design sessions and architecture decisions to finalize execution plans. It ensures alignment on data flow, edge cases, and performance criteria by providing interactive guidance and documented tradeoffs.