skills.rest
andrew-t-james
andrew-t-jamesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-eng-review

Identifies architectural decisions, data flows, edge cases, and test coverage in an engineering plan.

Updated Jul 3, 2025
Search Tags:#planning#architecture#edge-cases#recommendations#test-coverage#data-flow#engineering-review
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill plan-eng-review-andrew-t-james
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/plan-eng-review
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill plan-eng-review-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng teams need structured, repeatable reviews of architecture, data flow, edge cases, and test coverage to improve plan quality and reduce risk during handoffs and delivery.

Core Features & Use Cases

  • Structured, interactive reviews that surface architecture decisions, data flows, and risk factors.
  • Guidance on test coverage, edge cases, and performance implications for the active plan.
  • Use case: when evaluating a new module, run plan-eng-review to surface gaps, recommended tests, and deployment considerations.

Quick Start

Launch plan-eng-review on the current feature branch to start a guided engineering review.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
How do I conduct an architecture review for a new engineering plan?▼

Run a structured engineering review on your feature branch to surface architectural decisions, data flows, edge cases, and recommended test coverage to reduce delivery risk.

What is the best way to validate test coverage and edge cases before a design handoff?▼

Use a structured engineering review to evaluate test coverage and edge cases, surfacing risk flags and deployment considerations to ensure requirements are explicit and measurable before handoff.

When do I need a structured engineering review for my architecture decisions?▼

You need a structured engineering review when evaluating a new module, preparing for design handoffs, or performing post-implementation validation to surface architecture gaps and deployment risks.

Can I use a guided engineering review for post-implementation validation?▼

Yes, guided engineering review supports post-implementation validation by checking architectural decisions, data flows, and test coverage to ensure requirements remain explicit with measurable criteria after deployment.

How do I surface risk flags and mitigations in my engineering plan?▼

Review the active engineering plan to identify critical architectural decisions and edge cases, ensuring requirements are explicit with measurable criteria, risk flags, and recommended mitigations.

Related Skills

Explore More Software Engineering Skills→
ShaheerKhawajaShaheerKhawaja
8

plan-eng-review

Generate structured architecture reviews with data flows, error paths, and test matrices.

Community
Advanced
masta-g3masta-g3
1

test-coverage

Analyze test coverage and identify gaps with recommended tests.

Community
Intermediate
florianhornerflorianhorner
4

plan-eng-review

Reviews engineering plans for architecture, data flow, edge cases, tests, and performance.

Community
Advanced
LetPeopleWorkLetPeopleWork
16

code-review-checklist

Evaluate code plans and implementations against structured review criteria with severity levels.

Official
Basic