plan-eng-review

Reviews implementation plans for architecture, code quality, tests, and performance before coding begins.

107|7|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/no-session/pstack --skill plan-eng-review-no-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/no-session/pstack/tree/main/plan-eng-review
Command: npx skills add https://github.com/no-session/pstack --skill plan-eng-review-no-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo builders often jump from plan to code without an engineering review, so architecture flaws, missing edge cases, and untested codepaths only surface after implementation. This Skill runs an interactive engineering-manager-style review of a plan or design doc, catching problems while they are still cheap to fix. ## Core Features & Use Cases - Scope Challenge (Step 0): Checks whether existing code already solves sub-problems, flags scope creep, and challenges plans touching 8+ files or 2+ new services. - Section-by-Section Review: Walks through Architecture, Code Quality, Tests, and Performance interactively, raising one issue per AskUserQuestion with an opinionated recommendation. - Test Coverage Tracing: Detects the project's test framework, traces every planned codepath, and produces a coverage diagram so the plan includes full test coverage from the start. - Use Case: You have a design doc for a new billing feature and are about to start coding. Run this Skill to lock the architecture, expose a missing webhook retry edge case, and add tests for every branch before writing a line of code. ## Quick Start Ask the AI to run an engineering review of the current plan or design doc on this branch before starting implementation.

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 implementation plan before writing code?

Run an engineering plan review that checks scope, architecture, code quality, tests, and performance section by section. Each issue is presented individually with an opinionated recommendation, and you accept or reject changes before the plan is locked.

What does an engineering plan review check for?

It checks whether existing code already solves sub-problems, flags scope creep beyond 8 files or 2 new services, evaluates architecture and coupling, traces every planned codepath for test coverage, and reviews performance and edge cases.

Does the plan review work without a design doc?

Yes. If no design doc is found for the branch, it offers to run a validation step first to produce a structured problem statement, or proceeds with a standard review of whatever plan you provide.

How does the review detect my test framework?

It first reads the Testing section of CLAUDE.md, then falls back to auto-detection by checking for files like package.json, Gemfile, pytest.ini, or jest and vitest configs. If no framework is found, it still produces the coverage diagram but skips test generation.

When should I not run a full plan review?

Skip it for trivial changes where the plan is a few lines and touches one file. The review is designed for plans with real architectural decisions, new codepaths, or multiple components where catching issues early saves rework.