plan-eng-review

Review engineering architecture and lock in execution plans.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill plan-eng-review-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/plan-eng-review
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill plan-eng-review-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng teams often struggle to align on architecture and planning before coding. This Skill provides an interactive, structured plan-review workflow that locks in the execution strategy for architecture, data flow, diagrams, edge cases, test coverage, and performance.

Core Features & Use Cases

  • Interactive architecture review with opinionated recommendations.
  • Coverage of data flow, diagrams, edge cases, tests, and performance criteria.
  • Proactive assistance when a design doc or plan is present to surface issues before implementation.
  • Use cases: when asked to "review the architecture", "engineering review", or "lock in the plan", or when starting a coding effort that needs a validated plan.

Quick Start

Ask me to load the current plan and run a guided engineering review.

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 before starting implementation?

Architecture review evaluates your design doc to lock in the execution plan, covering data flow, edge cases, test coverage, and performance. It provides structured problem statements, evaluated tradeoffs, and actionable recommendations to guide teams from design to coding.

What is an engineering review for a coding plan?

An engineering review is an interactive workflow that validates your execution strategy before coding begins. It proactively surfaces architecture and planning issues from a design doc to prevent coding mistakes, ensuring alignment on data flow, diagrams, and performance criteria.

How do I lock in the execution plan for a new software feature?

Lock in an execution plan by running a guided architecture review that assesses tradeoffs, edge cases, and test coverage. This interactive process ensures the team validates the design doc and aligns on the implementation strategy before writing any code.

Can I use an architecture review on an existing design doc?

Yes, when a design doc or plan is present, the engineering review proactively surfaces issues to prevent coding mistakes. It evaluates the existing architecture, data flow, and performance criteria to provide actionable recommendations for the implementation phase.

What's the best way to evaluate tradeoffs in an architecture design doc?

Evaluating tradeoffs in a design doc requires a structured engineering review that analyzes architecture, data flow, and edge cases. This interactive process provides opinionated recommendations and actionable guidance to ensure the team validates execution strategy before implementation.

What should an engineering review cover to prevent coding mistakes?

To prevent coding mistakes, an engineering review should cover architecture, data flow, diagrams, edge cases, test coverage, and performance. Locking in these execution plan details ensures the team identifies potential issues early in the design phase.