plan-eng-review

Review engineering plans across architecture, code quality, test coverage, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the common failure mode where engineering plans are created but lack rigorous scrutiny, leading to architectural flaws, missed edge cases, and technical debt before a single line of code is written.

Core Features & Use Cases

  • Structured Review: Executes a mandatory four-section review covering architecture, code quality, test coverage, and performance.
  • Independent Challenge: Automatically invokes an outside voice (Codex or subagent) to provide a second, critical opinion on the plan.
  • Use Case: Before starting a complex feature, use this skill to ensure your data flow, security boundaries, and test strategy are robust, catching potential production failures early.

Quick Start

Invoke the plan-eng-review skill to perform a technical review of the current engineering 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 before implementation to catch architecture flaws?

Review your engineering plan by running a rigorous, multi-stage evaluation that checks system boundaries, code quality, test coverage, and performance bottlenecks before implementation begins.

What is independent cross-model verification for architecture and code review?

Independent cross-model verification is an automated process that invokes an outside voice, such as Codex or a subagent, to provide a second critical opinion on your technical plan.

How do I ensure all identified issues in a technical plan are addressed before coding?

Ensure issues are addressed through an interactive, gate-controlled approval process that blocks implementation until every architectural flaw and missed edge case is resolved.

When do I need a structured engineering review for my technical design?

You need a structured engineering review when starting a complex feature to ensure your data flow, security boundaries, and test strategy are robust, catching potential production failures early.

Does this engineering review process work without external dependencies?

Yes, the engineering review process operates independently without external dependencies, utilizing internal scripts to execute its four-section review and gate-controlled approval workflow.

Can I use this to evaluate system boundaries and performance bottlenecks in my plan?

Yes, you can evaluate system boundaries and performance bottlenecks as part of the mandatory four-section review covering architecture, code quality, test coverage, and performance.