plan-eng-review

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

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill plan-eng-review-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/plan-eng-review
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill plan-eng-review-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering managers and senior engineers thoroughly review execution plans to catch architectural oversights, unclear data flows, missing tests, performance risks, and edge-case gaps before code changes are made.

Core Features & Use Cases

  • Interactive Scope Challenge: Runs an initial Step 0 to identify existing solutions, propose a minimal scope, and surface scope-smells with a clear choice of three review modes.
  • Sectioned Review Workflow: Guided Architecture, Code Quality, Test, and Performance sections that halt for one decision per issue using AskUserQuestion and produce opinionated, tradeoff-based recommendations.
  • Diagram-first Guidance: Generates and enforces ASCII diagrams for data flow, state machines, and test coverage, and identifies files that need inline diagram upkeep.
  • Use Case: An engineering manager preparing a PR review uses this Skill to produce a prioritized issue list, ASCII diagrams, per-issue decision prompts, and a TODOS.md with contextual entries.

Quick Start

Use this skill to review an execution plan and produce a scoped, prioritized list of issues with ASCII diagrams and explicit tradeoff 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 review an engineering execution plan for architectural flaws and missing tests?

To review an engineering execution plan, you assess architecture, data flows, and test coverage to catch risks and edge-case gaps before coding. This process yields prioritized issues, ASCII diagrams, and tradeoff recommendations for managers.

How do I generate ASCII diagrams for data flow and state machines during a plan review?

Generating ASCII diagrams for data flow and state machines helps visualize logic during engineering plan reviews. This Skill automatically produces these diagrams to enforce scope constraints, identify files needing diagram upkeep, and guide interactive tradeoff decisions.

Can I use this plan review process for pull request evaluations and design proposals?

Yes, you can apply this plan review process to pull request evaluations and design proposals. It uses an interactive scope challenge and sectioned workflow to produce per-issue decision prompts, tradeoff recommendations, and a contextual TODOS list.

What is the best way to enforce scope constraints and check test coverage during a design proposal review?

The best way to enforce scope constraints and check test coverage is through an interactive Step 0 scope challenge followed by sectioned reviews. This approach surfaces scope-smells, proposes a minimal scope, and generates per-issue decision prompts to lock in robust engineering plans.

Why does my engineering plan review halt for a decision on every single issue?

Your engineering plan review halts for a decision on every issue to enforce interactive tradeoff analysis. By using AskUserQuestion for each identified architectural flaw or gap, it ensures you make an opinionated, prioritized remediation choice before proceeding to the next section.