plan-eng-review

Review architecture and execution plans for tradeoffs and completeness.

Updated Mar 22, 2026

Search Tags:#architecture #engineering #edge-cases #diagrams #test-coverage #data-flow #plan-review

Ready to run

npx skills add https://github.com/jm199seo/lostark-accessory-viewer --skill plan-eng-review-jm199seo

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides engineering teams through structured reviews of architecture and execution plans, ensuring decisions are deliberate and well-documented.

Core Features & Use Cases

Interactive plan-review sessions that cover architecture, data flow, edge cases, test coverage, and performance considerations.
Opinionated recommendations that help lock in the plan before coding, with clear trade-offs and next-step actions.
Proactive evaluation when a user has a plan or design doc, surfacing concerns early to catch issues before implementation.

Quick Start

Provide an engineering plan review for a feature or system design and receive a structured, actionable critique with prioritized 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 review an architecture plan before coding to catch edge cases?▼

Review an architecture plan by running interactive sessions that analyze data-flow, edge cases, and test coverage. This enforces structured prompts and completeness principles to surface tradeoffs, ensuring deliberate and well-documented decisions before implementation begins.

What is a structured engineering plan review and when do I need one?▼

A structured engineering plan review is a proactive evaluation of a system design or feature plan that covers architecture, performance, and data flow. You need one when you have a design doc ready and want to lock in decisions with clear trade-offs before coding starts.

How do I generate data-flow diagrams and test coverage analysis for a system design?▼

Generate data-flow diagrams and test coverage analysis by providing your system design to an interactive review session. The session evaluates your plan across modules, surfacing performance considerations and completeness principles to produce an actionable critique with prioritized recommendations.

Can I use an interactive plan review for any software engineering module?▼

Yes, you can use an interactive plan review for any software engineering module. The review supports architecture, data-flow analysis, and performance planning across modules by enforcing structured prompts and interactive questions to surface tradeoffs specific to your system design.

What is the best way to evaluate tradeoffs in an execution plan?▼

The best way to evaluate tradeoffs in an execution plan is through an opinionated review that enforces completeness principles and interactive questions. This surfaces clear trade-offs and next-step actions, helping engineering teams lock in the plan before coding.

Why should I not start coding without a proactive architecture evaluation?▼

Starting coding without a proactive architecture evaluation risks overlooking edge cases, data-flow bottlenecks, and test coverage gaps. A structured plan review surfaces these concerns early, providing clear trade-offs and prioritized recommendations to catch issues before implementation.