skills.rest
alexandervashurin
alexandervashurinCOMMUNITY
Explore all skills by this author →
GitHub

plan-eng-review

Review engineering plans for risks, tradeoffs, and actionable improvements.

1|Updated Feb 25, 2026
Search Tags:#design#architecture#engineering#risk-assessment#code-review#plan-review
One-click install
npx skills add https://github.com/alexandervashurin/semaphore --skill plan-eng-review-alexandervashurin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/alexandervashurin/semaphore/tree/main/.claude/skills/plan-eng-review
Command: npx skills add https://github.com/alexandervashurin/semaphore --skill plan-eng-review-alexandervashurin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan ambiguity and scope creep cripple engineering projects. This skill provides a structured, opinionated plan-review workflow that surfaces risks, tradeoffs, and concrete next steps before coding begins.

Core Features & Use Cases

  • Stepwise evaluation of architecture, data flow, tests, and performance with explicit tradeoffs.
  • Interactive AskUserQuestion style prompts to surface decisions and align stakeholders.
  • Generates a formal test plan artifact and notes NOT IN SCOPE to keep scope tight.

Quick Start

Provide a structured plan review by examining the design doc and constraints and returning actionable recommendations.

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 engineering plan review for architecture and data flow?▼

An engineering plan review evaluates design docs to identify risks, tradeoffs, and concrete improvements across architecture, data flow, tests, and performance before coding begins.

What is a structured design review and when do I need it for code planning?▼

A structured design review is an opinionated evaluation of engineering plans to identify risks and scope creep, needed when architecture ambiguity threatens project boundaries before coding begins.

How do I identify tradeoffs and risks in an architecture design doc?▼

Identify tradeoffs and risks in an architecture design doc through stepwise evaluation of data flow and performance constraints, surfacing TODOs and design notes to produce actionable recommendations.

Can I use this to generate a formal test plan and define what is NOT IN SCOPE?▼

Yes, this generates a formal test plan artifact and explicit NOT IN SCOPE boundaries to keep scope tight, producing structured recommendations while aligning stakeholders through interactive decision prompts.

What is the best way to prevent scope creep in software engineering plans?▼

The best way to prevent scope creep is to conduct an end-to-end plan review applying a Boil the Lake approach for completeness, explicitly noting out-of-scope items and generating actionable next steps.

Related Skills

Explore More Software Engineering Skills→
stayconnectquickstayconnectquick

plan-eng-review

Guide interactive engineering-plan reviews covering architecture, data flow, edge cases, test coverage, and performance.

Community
Advanced
CenredJunCenredJun

plan-eng-review

Review engineering execution plans for architectural flaws, data flow issues, and missing tests.

Community
Advanced
cipherstashcipherstash
17

Validating Review Feedback

Validate code review feedback against the implementation plan to prevent scope creep.

Official
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced