plan-eng-review

Identify and lock in execution plans for engineering and architecture reviews.

10|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill plan-eng-review-olaafrossi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/plan-eng-review
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill plan-eng-review-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng managers need a structured, repeatable way to lock in execution plans for complex architectures, data flows, and performance considerations before coding begins.

Core Features & Use Cases

  • Interactive architecture reviews with opinionated recommendations.
  • Clear data-flow diagrams and guardrails for edge cases and test coverage.
  • Proactive planning when a design doc or plan exists, helping teams align quickly.

Quick Start

Say 'review the architecture' to start a guided Eng plan 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 an architecture plan before implementation?

An engineering review evaluates your design doc to identify required artifacts, check edge cases, and provide concrete recommendations for implementation readiness. It ensures data-flow diagrams and test coverage guardrails are established before coding begins.

What is an architecture plan lock-in?

An architecture plan lock-in is the process of finalizing execution plans for complex architectures and data flows. It applies structured checks to align engineering teams on performance considerations and required artifacts before development starts.

Can I use this engineering review if I only have a basic design doc?

Yes, a design doc or plan is sufficient to start a guided engineering review. The process applies when a design doc is available for critique, providing opinionated recommendations and required artifacts to guide the review from problem statement to implementation readiness.

How do I identify edge cases and test coverage gaps in my data-flow diagrams?

To identify edge cases and test coverage gaps, an architecture review examines your data-flow diagrams and establishes guardrails. It proactively checks the design doc to ensure edge-case considerations and test coverage requirements are documented before implementation.

What's the best way to align engineering teams on complex architecture plans?

The best way to align teams is through an interactive architecture review with opinionated recommendations. By locking in an execution plan with clear data-flow diagrams and edge-case guardrails, teams can quickly agree on implementation readiness and required artifacts.