skills.rest
cegit27
cegit27OFFICIAL
Explore all skills by this author →
GitHub

plan-eng-review

Review engineering plans to validate architecture, data flow, and test coverage.

3|14|Updated Mar 10, 2026
Search Tags:#architecture#test coverage#design review#technical review#execution plan#plan review#engineering review
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill plan-eng-review-cegit27
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill plan-eng-review-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting implementation without validating architecture leads to rework, technical debt, and missed edge cases that are expensive to fix later.

Core Features & Use Cases

  • Architecture & Data Flow Review: Validates system design, component interactions, and data flow before coding begins.
  • Test Coverage & Edge Case Analysis: Identifies gaps in testing strategy and flags failure modes early.
  • Use Case: A team preparing to build a new authentication service can use this skill to review API contracts, database schemas, and error handling paths before writing any code.

Quick Start

Use the plan-eng-review skill to review the attached architecture diagram and implementation plan for the new authentication service.

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 execution plan to catch architecture flaws before implementation?▼

Review execution plans by validating architecture, data flow, and test coverage interactively to catch design flaws, edge cases, and performance bottlenecks before coding begins.

Why does starting implementation without an engineering plan review lead to rework?▼

Starting implementation without an engineering plan review leads to rework because undetected architecture flaws, missed edge cases, and technical debt become expensive to fix later in the development cycle.

What is the best way to validate API contracts and database schemas before coding?▼

The best way to validate API contracts and database schemas is performing an interactive engineering plan review to evaluate system design, component interactions, and error handling paths.

Can I use a technical review to identify gaps in my test coverage and failure modes?▼

Yes, a technical review can identify gaps in test coverage and flag failure modes early by performing structured evaluation of testing strategy and edge case analysis before implementation.

Does an engineering plan review work for evaluating component interactions and data flow?▼

Yes, an engineering plan review works for evaluating component interactions and data flow by validating system design and architecture to ensure execution plans are structurally sound.

When do I need to run a design review on my technical specifications?▼

You need to run a design review on technical specifications when preparing to build a new service and needing opinionated recommendations to evaluate execution plans before committing to implementation.

Related Skills

Explore More Software Engineering Skills→
yckkkkyckkkk
1

plan-eng-review

Guide engineering review workflows to lock in architecture and test strategies.

Community
Advanced
OzeroHAXOzeroHAX
32

planning-migration-strategy

Designs phased data migration strategies for schemas, data, and contracts.

Community
Intermediate
weirdgmeweirdgme
4

error-tracking

Integrate Sentry v8 error tracking and performance monitoring across project services.

Community
Advanced
agnaldo4jagnaldo4j
1

circular-dependency-control

Detect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.

Community
Advanced