skills.rest
gth-ai
gth-aiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-eng-review

Review technical plans for architecture, code quality, test coverage, and performance.

1|Updated Oct 9, 2025
Search Tags:#planning#architecture#quality assurance#code review#technical design#engineering
One-click install
npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill plan-eng-review-gth-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/gth-ai/hadriengayap.github.io/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/gth-ai/hadriengayap.github.io --skill plan-eng-review-gth-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the lack of thoroughness in technical planning by enforcing a structured, opinionated review process that catches architectural flaws, edge cases, and scope creep before code is written.

Core Features & Use Cases

  • Structured Review: Guides the user through architecture, code quality, testing, and performance sections with mandatory stops for feedback.
  • Scope Control: Challenges the user to define the minimum viable change and identify existing solutions to prevent over-engineering.
  • Use Case: Before starting a complex refactor or a new feature, use this Skill to validate your design, ensure test coverage, and identify potential production failure modes.

Quick Start

Activate the plan-eng-review skill to begin a comprehensive architectural and code quality assessment of your current project 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 a technical design document before starting to code?▼

To review a technical design document, you need a structured process that evaluates architectural integrity, code quality, test coverage, and performance bottlenecks through interactive feedback loops to ensure robust implementation.

What is the best way to prevent scope creep during engineering planning?▼

Preventing scope creep during engineering planning requires challenging the team to define the minimum viable change and identify existing solutions, which stops over-engineering before any code is actually written.

How do I identify potential production failure modes in my architecture?▼

Identifying potential production failure modes requires enforcing strict failure mode analysis within your engineering plan, evaluating architectural flaws and edge cases to guarantee maintainable software implementations.

Does a structured engineering plan review work for complex refactoring?▼

A structured engineering plan review works for complex refactoring by validating your design, ensuring adequate test coverage, and identifying performance bottlenecks before the actual implementation begins.

When should I use an opinionated engineering review process?▼

You should use an opinionated engineering review process when starting complex refactors or new features to catch architectural flaws, edge cases, and scope creep early, ensuring robust and maintainable software.

Related Skills

Explore More Software Engineering Skills→
ryryoryryo
3

dev:ideation

Convert product ideas into structured specifications with JTBD analysis and SLC framing.

Community
Advanced
yocxy2yocxy2

plan-eng-review

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

Community
Advanced
dorriodorrio

ln-782-test-runner

Execute all defined test suites and generate code coverage reports.

Community
Intermediate
tom-xstom-xs

requesting-code-review

Dispatch a subagent to evaluate git diffs against defined requirements.

Community
Advanced