skills.rest
cropsgg
cropsggCOMMUNITY
Explore all skills by this author →
GitHub

plan-eng-review

Review multi-service plans for architecture, data flow, edge cases, and test coverage.

15|5|Updated May 17, 2026
Search Tags:#architecture#mermaid#diagramming#review#edge-cases#data-flow#test-plan
One-click install
npx skills add https://github.com/cropsgg/skills --skill plan-eng-review-cropsgg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/cropsgg/skills/tree/main/skills/planning/plan-eng-review
Command: npx skills add https://github.com/cropsgg/skills --skill plan-eng-review-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning reviews are often rushed or incomplete, leading to misaligned architecture, unclear data flows, missing edge cases, and gaps in test coverage. This skill standardizes pre-implementation reviews to surface hidden assumptions and define verifiable criteria.

Core Features & Use Cases

  • Diagram-driven review: require at least one diagram (sequence, component, or data flow) to reveal architecture decisions and dependencies.
  • Explicit guarantees: require timeouts, retry policies, and defined failure behaviors for every external call.
  • Edge-case and test-matrix planning: capture boundary conditions and map them to unit/integration/e2e tests; provide a migration/rollback plan when applicable.
  • Use Case: before a major refactor or migration that touches multiple services, run plan-eng-review to lock the plan and acceptance criteria.

Quick Start

Provide a comprehensive architecture review and test plan for a multi-service plan before coding.

Frequently Asked Questions about plan-eng-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I lock architecture and test coverage before implementation?▼

To lock architecture before implementation, apply a formal review process that requires diagrams, explicit timeouts, retry policies, and an edge-case test matrix to define verifiable acceptance criteria.

What is a diagram-driven architecture review for multi-service plans?▼

A diagram-driven architecture review requires sequence, component, or data-flow diagrams to reveal architecture decisions and dependencies for plans spanning multiple services, databases, or async boundaries.

How do I map edge cases to a test plan for a major refactor?▼

To map edge cases to a test plan, capture boundary conditions in a formal matrix and map them directly to unit, integration, and e2e tests, while providing a migration and rollback plan.

Do I need explicit timeouts and retry policies for external calls in my design?▼

Yes, explicit timeouts, retry policies, and defined failure behaviors are required for every external call to surface hidden assumptions and ensure a coherent multi-service design.

When should I run a pre-implementation architecture review?▼

Run a pre-implementation architecture review before a major refactor or migration that touches multiple services, databases, or async boundaries to lock the plan and acceptance criteria.

Related Skills

Explore More Software Engineering Skills→
TrecekTrecek
1

make-arch-diag

Generate component, data flow, and sequence diagrams in mermaid syntax.

Community
Advanced
nullmastermindnullmastermind
9

test

Plan and scope testing work with coverage maps and prioritized task lists.

Community
Intermediate
mjunaidcamjunaidca
9

mermaid-diagram

Convert educational content into Mermaid diagrams with alt text and captions.

Community
Basic
howdeployhowdeploy
15

plan-eng-review

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

Community
Advanced