plan-eng-review

Orchestrate engineering plan reviews covering architecture, data flow, and test coverage.

5|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill plan-eng-review-drt0927
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-plan-eng-review
Command: npx skills add https://github.com/drt0927/tw-overlay --skill plan-eng-review-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering teams often struggle to align on architecture and execution plans before coding, leading to costly rework and miscommunications.

Core Features & Use Cases

  • Interactive engineering plan reviews that lock in architecture, data flow, diagrams, edge cases, test coverage, and performance expectations.
  • Proactive recommendations and structured trade-offs to help leaders decide on design choices before implementation.
  • Guided, step-by-step plan validation with artifacts that can be attached to the project timeline for clarity.

Quick Start

Start a plan review by stating the intent: ask for an architecture review or engineering plan as the trigger.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
How do I conduct an engineering plan review to align teams before coding?

An engineering plan review aligns teams before coding by interactively surfacing architecture decisions, data flow, risk assessment, and test coverage. You trigger the review by simply requesting an architecture review or engineering plan validation.

What is an architecture design review and when do I need one for complex systems?

An architecture design review evaluates design choices and trade-offs for complex systems before implementation. You need one when engineering teams must align on execution plans, data flow, and edge cases to prevent costly rework and miscommunications.

Can I use an interactive engineering plan review to assess architecture risks and test coverage?

Yes, an interactive engineering plan review can assess architecture risks and test coverage. It uses step-by-step guided prompts to gather acceptance criteria, surface edge cases, and produce structured trade-offs for leaders to validate performance expectations.

What is the best way to document architecture decisions and data flow for a project timeline?

The best way to document architecture decisions is through a structured plan review that generates artifacts with data flow, diagrams, and risk assessments. These artifacts can be attached directly to your project timeline for team clarity and execution planning.

What should an architecture review cover to prevent miscommunications during execution planning?

An architecture review should cover architecture decisions, data flow, edge cases, test coverage, and performance expectations. Proactively surfacing these structured trade-offs prevents miscommunications and aligns teams on design choices before implementation begins.