skills.rest
tyhuffman7
tyhuffman7COMMUNITY
Explore all skills by this author →
GitHub

plan-eng-review

Reviews engineering plans for architecture, data flow, diagrams, edge cases, test coverage, and performance.

1|Updated Apr 15, 2026
Search Tags:#testing#architecture#performance#engineering#data-flow#design-review#plan-review
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill plan-eng-review-tyhuffman7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-plan-eng-review
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill plan-eng-review-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng managers and engineering teams struggle to align on architecture, data flows, diagrams, edge cases, test coverage, and performance before code is written. This Skill provides a repeatable, structured plan-review workflow that surfaces risks early and unblocks delivery.

Core Features & Use Cases

  • Structured engineering plan review covering architecture, data flow, diagrams, edge cases, tests, and performance.
  • Opinionated recommendations and prompts to align stakeholders and accelerate decision-making.
  • Use cases include evaluating a design doc, locking in the plan before implementation, or performing a pre-release review.

Quick Start

Start the eng plan review for the current sprint by running /plan-eng-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 conduct an engineering plan review before coding begins?▼

An engineering plan review evaluates architecture, data flow, diagrams, edge cases, test coverage, and performance to surface risks early and align stakeholders before implementation. It provides a structured, opinionated evaluation to unblock delivery and improve design quality.

What is design-drift checking in a software architecture review?▼

Design-drift checking is a pre-release review process that locks in the execution plan for architecture reviews, ensuring the actual implementation conforms to the original design doc. It enforces structured evaluation to surface gaps and prevent deviations from approved plans.

How do I evaluate edge cases and test coverage in a design doc?▼

Evaluating edge cases and test coverage in a design doc requires a structured plan review that examines data flow and architecture to identify potential failure points. This opinionated evaluation surfaces gaps to improve design quality before any coding starts.

Does this engineering plan review workflow require specific dependencies?▼

This engineering plan review workflow requires no specific dependencies or external components. It functions as a standalone, opinionated evaluation process to align engineering teams on architecture, data flows, and performance without needing specialized tooling.

When should I use a structured plan review instead of a standard code review?▼

Use a structured plan review to lock in architecture, data flows, and test coverage before code is written, whereas a standard code review happens post-implementation. This pre-coding evaluation surfaces design risks early, preventing costly rework and design drift.

Related Skills

Explore More Software Engineering Skills→
him55710-sudohim55710-sudo

plan-eng-review

Outline an execution plan covering architecture, data flow, diagrams, edge cases, and tests.

Community
Advanced
thesaifalitaithesaifalitai
8

test-master

Write and execute software tests for functionality, performance, and security.

Community
Advanced
Imad-OuteImad-Oute
2

mh-cto-sdlc-cicd-gates

Design CI/CD pipelines with quality gates and integrated test plans.

Community
Advanced
StudentCristianStudentCristian

nw-sa-critique-dimensions

Evaluate solution architecture documents using structured critique dimensions for quality issues.

Community
Advanced