plan-eng-review

Analyze engineering plans and generate architecture, data flow, and risk assessments.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams need structured, evidence-backed plan reviews to validate architecture, data flows, edge cases, tests, and performance before building.

Core Features & Use Cases

  • Stepwise review prompts that cover architecture, data flow, diagrams, edge cases, test coverage, and performance.
  • ASCII diagram guidance and in-code comments to help maintain diagrams alongside design notes.
  • Collaborative workflow prompts for plan refinement, risk assessment, and decision logging.

Quick Start

Provide your current architecture, data flows, and top risks to start the plan review.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
What is an engineering plan review and what does it cover?

An engineering plan review is a structured analysis of system designs covering architecture, data flow, edge cases, test coverage, and performance to validate decisions before building. It ensures documentation of scope, trade-offs, and testability for complex modules and services.

How do I review an architecture plan for complex system designs?

Review an architecture plan by providing your current architecture, data flows, and top risks to trigger stepwise review prompts. This generates a decision-ready critique with architecture assessments, risk evaluations, and trade-off notes for complex modules and services.

Can I generate ASCII diagrams for data flow and architecture documentation?

Yes, you can generate ASCII diagram guidance for data flow and architecture documentation. The review process includes in-code comments to help maintain diagrams alongside design notes, ensuring visual representations stay integrated with system specifications.

Does the plan review process support interactive critique for risk assessment?

Yes, the plan review process supports interactive critique for risk assessment. It provides collaborative workflow prompts for plan refinement and decision logging, helping engineering teams evaluate trade-offs and document architectural decisions iteratively.

What's the best way to document trade-offs and testability in software engineering plans?

The best way to document trade-offs and testability in software engineering plans is through guided review workflows. This approach systematically evaluates edge cases, performance metrics, and test coverage, producing a comprehensive, decision-ready plan review with detailed notes.

When do I need a structured plan review for my engineering architecture?

You need a structured plan review when validating architecture, data flows, edge cases, tests, and performance before building complex system designs. It is essential when engineering teams require evidence-backed validation and documentation of scope and trade-offs.