skills.rest
abrahamgreyson
abrahamgreysonCOMMUNITY
Explore all skills by this author →
GitHub

plan-eng-review

Review engineering plans for architecture, data flow, test coverage, and performance.

Updated Aug 27, 2026
Search Tags:#architecture#performance#implementation plan#test coverage#technical review#engineering review
One-click install
npx skills add https://github.com/abrahamgreyson/skills --skill plan-eng-review-abrahamgreyson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/abrahamgreyson/skills/tree/main/gstack/plan-eng-review
Command: npx skills add https://github.com/abrahamgreyson/skills --skill plan-eng-review-abrahamgreyson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate an engineering plan before implementation begins, so architecture mistakes, missing tests, and performance risks are caught early instead of after code is written.

Core Features & Use Cases

It guides an interactive review of the proposed design, including system boundaries, data flow, edge cases, security concerns, test coverage, and performance tradeoffs. It also challenges the plan from multiple angles, highlights gaps that need explicit approval, and can surface a second outside opinion when useful. Use it when you have a design doc, implementation outline, or scoped feature and want a rigorous technical review before development starts.

Quick Start

Ask me to review your engineering plan and I will walk through the architecture, implementation risks, test coverage, and performance concerns with you.

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 before implementation starts?▼

To review an engineering plan, you need an interactive process that analyzes architecture, data flow, test coverage, and performance. This approach validates design docs and scoped features to catch system boundary gaps and performance tradeoffs early.

What is a technical engineering review and when do I need one?▼

A technical engineering review evaluates proposed changes for architecture risks, missing tests, and security concerns. You need this rigorous review when you have a design doc or implementation outline and want to validate technical tradeoffs before development.

Can I use an engineering review to check test coverage and performance risks?▼

Yes, an engineering review can check test coverage and performance risks by providing plan-ready test guidance and explicit risk calibration. It challenges your implementation outline from multiple angles to highlight gaps requiring approval.

What's the best way to analyze architecture and data flow in a design doc?▼

The best way to analyze architecture and data flow is through an issue-by-issue analysis that challenges the proposed design. This interactive review assesses system boundaries, edge cases, and performance tradeoffs to surface a second outside opinion.

Does an engineering review work for scoped features and proposed changes?▼

Yes, engineering reviews work for scoped features and proposed changes. They apply rigorous technical review to validate implementation plans, ensuring data flow architecture and test coverage are evaluated before coding begins.

Related Skills

Explore More Software Engineering Skills→
CraigtutCraigtut
1

doc-explorer

Load foundational Animus docs and explore topic-specific project documentation.

Community
Intermediate
romiluz13romiluz13
161

planning-patterns

Generate executable, test-driven implementation plans with explicit file changes and commit actions.

Community
Advanced
howdeployhowdeploy
15

plan-eng-review

Coordinate and lock in engineering plans for architecture, data flow, edge cases, test coverage, and performance.

Community
Advanced
tamago0224tamago0224

golang-security

Identify security vulnerabilities in Go code using govulncheck and static analysis.

Community
Advanced