plan-eng-review

Guide engineering plan reviews to surface architecture and design risks before coding.

2|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill plan-eng-review-omerfarukoruc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/OmerFarukOruc/symphony-orchestrator/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/OmerFarukOruc/symphony-orchestrator --skill plan-eng-review-omerfarukoruc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides and standardizes engineering plan reviews to surface architecture, data flow, edge cases, and test coverage issues before coding starts.

Core Features & Use Cases

  • Structured review workflow that surfaces risks, trade-offs, and validation criteria early in the development life cycle.
  • Interactive prompts, checklists, and decision records to ensure design decisions are thoroughly examined.
  • Artifact generation (review notes, scope decisions, and test-plan outlines) suitable for PRs and design documentation.

Quick Start

Ask plan-eng-review to start a structured engineering plan review for your feature and surface risks, tradeoffs, and a recommended plan.

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 engineering plan to surface architecture and design risks before coding?

Reviewing an engineering plan involves validating architecture, data flow, and edge cases early. This Skill guides structured plan reviews using interactive prompts and checklists to surface trade-offs and ensure completeness before development starts.

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

A structured engineering plan review is a validation process applied during feature intake and design discussions. You need it to mitigate risks and examine design decisions thoroughly before committing to code implementation.

How do I generate test-plan outlines and review notes for a design document?

To generate test-plan outlines and review notes for design documentation, use a structured plan review workflow. It produces artifacts like scope decisions and validation criteria suitable for pull requests and design docs.

Can I use this workflow for interactive decision making during feature intake?

Yes, you can use this workflow for interactive decision making during feature intake. It enforces a frontmatter-driven process that supports interactive prompts and generates checklists to guide design decisions.

What is the best way to validate design completeness and identify trade-offs?

The best way to validate design completeness is through a standardized review process that examines architecture and test coverage. This approach surfaces trade-offs and validation criteria early in the development lifecycle.

Do I need any specific dependencies to run a structured plan review?

No specific dependencies are required to run a structured plan review. The Skill operates independently to guide engineering plan validation, generate artifacts, and support interactive decision making.