plan-eng-review

Automate architecture and design reviews for engineering plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlined, rigorous engineering plan reviews that surface architecture decisions, tradeoffs, and risks before coding starts.

Core Features & Use Cases

  • Structured review workflow with sections for scope, constraints, and edge cases.
  • Interactive prompts to guide architecture discussions, diagrams, and test plans.
  • Use cases across software projects: from MVPs to large-scale systems, across teams.

Quick Start

Run a plan-eng-review session on the current branch to begin a structured architecture 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 engineering design doc for architecture risks before coding?

To review an engineering design doc, you need a structured workflow that surfaces architecture risks, tradeoffs, and edge cases. This process enforces plan structure by evaluating scope, data flow, and testing strategies to ensure safer software projects.

What should be included in an architecture plan review?

An architecture plan review should include sections for scope, constraints, and edge cases. It must guide discussions around data flow, interfaces, risks, and measurable criteria, ensuring tradeoffs are documented before development starts.

Can I use a structured plan review for both MVP and large-scale system design?

Yes, structured plan reviews apply across software projects ranging from MVPs to large-scale systems. The review process scales by enforcing architecture decisions, testing strategies, and measurable criteria regardless of project size.

How do I start a plan review session on my current branch?

You start a plan review session by running the review process on your current branch. This initiates interactive prompts that guide architecture discussions, diagrams, and test plans for your engineering design.

Why do I need to document tradeoffs and edge cases in a software design doc?

Documenting tradeoffs and edge cases in a software design doc unlocks safer architecture by rigorously evaluating risks before coding starts. This structured approach ensures constraints and measurable criteria are fully addressed.

Does automated design review work without external dependencies?

Yes, automated design review works without external dependencies. It relies on interactive prompts to guide architecture discussions and enforce plan structure, requiring no additional components to evaluate testing strategies and data flow.