skills.rest
CODE-SAURABH
CODE-SAURABHCOMMUNITY
Explore all skills by this author →
GitHub

plan-eng-review

Stress-test engineering plans for architectural flaws and testing gaps.

2|1|Updated Jul 25, 2026
Search Tags:#architecture#api design#edge cases#data modeling#test planning#migration safety#engineering plan review
One-click install
npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill plan-eng-review-code-saurabh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/CODE-SAURABH/OpenSkills/tree/main/plan-eng-review
Command: npx skills add https://github.com/CODE-SAURABH/OpenSkills --skill plan-eng-review-code-saurabh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill exposes hidden assumptions, architectural risks, data-model flaws, failure modes, and testing gaps before engineering work begins, helping teams prevent expensive rework and production incidents.

Core Features & Use Cases

  • Architecture Review: Evaluate component boundaries, data flows, API contracts, dependencies, and asynchronous interactions.
  • Risk and Schema Analysis: Identify concurrency issues, scalability risks, migration hazards, input boundaries, authorization gaps, and recovery requirements.
  • Test Planning: Produce structured unit, integration, end-to-end, edge-case, coverage, and approval criteria for the proposed implementation.
  • Use Case: Apply it to a checkout, webhook, queue-based workflow, or database migration plan to turn an ambiguous proposal into an implementation-ready engineering document.

Quick Start

Use the plan-eng-review skill to review the attached feature specification and implementation plan, identify risks and open questions, and produce a final engineering review with diagrams, schema analysis, test coverage, and approval conditions.

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 for architectural flaws and hidden risks before implementation?▼

Engineering plan review stress-tests design documents to uncover architectural flaws, hidden assumptions, and data-model risks before implementation begins. It evaluates component boundaries, data flows, and API contracts to prevent expensive rework and production incidents.

What is the best way to stress-test a database migration plan for failure modes?▼

Stress-testing a database migration plan identifies schema hazards, concurrency issues, and recovery requirements. It analyzes migration decisions and data-model risks to ensure production safety and validate rollback strategies before deployment.

How do I identify edge cases and testing gaps in an API design proposal?▼

Identifying edge cases in API design involves evaluating input boundaries, authorization gaps, and dependency failure handling. A thorough review produces structured unit, integration, and end-to-end test plans to ensure complete coverage and approval readiness.

Can I use an engineering plan review for asynchronous workflows and multi-service systems?▼

Engineering plan review applies directly to asynchronous workflows and multi-service systems. It evaluates asynchronous interactions, dependency failures, and component responsibilities to expose scalability risks and hidden assumptions in distributed architectures.

What components do I need to include in a feature specification for a technical approval review?▼

A feature specification for technical approval requires documented component responsibilities, data flows, schema decisions, concurrency analysis, and edge-case coverage. Including detailed test plans and migration decisions ensures a comprehensive engineering review.

When should I not use an automated architecture review for my software project?▼

Architecture review should not be used when implementation has already begun or when the plan lacks documented data flows and component responsibilities. It requires a detailed specification to evaluate API contracts, schema decisions, and testing gaps effectively.

Related Skills

Explore More Software Engineering Skills→
ValerianGuivarchValerianGuivarch

technical-scoping

Convert macro-scoping documents into technical specifications with API contracts and data models.

Community
Advanced
bdbchbdbch
2

test-strategy

Assess and plan test strategies for software features and refactors.

Community
Intermediate
Eigo-Mt-FujiEigo-Mt-Fuji

database-schema-designer

Design database schemas, ER diagrams, and DDL for relational and NoSQL databases.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced