skills.rest
jokerman89
jokerman89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-eng-review

Reviews implementation plans for architecture, code quality, test coverage, and performance before shipping.

Updated May 27, 2026
Search Tags:#architecture#code review#performance#test coverage#quality gate#plan review#lintel
One-click install
npx skills add https://github.com/jokerman89/lintel --skill plan-eng-review-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/jokerman89/lintel/tree/main/skills/plan-eng-review
Command: npx skills add https://github.com/jokerman89/lintel --skill plan-eng-review-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering plans often ship with scope creep, missing test coverage, and unexamined architecture decisions. This Skill enforces a structured technical review gate so a plan or change is validated for engineering soundness before implementation or release. ## Core Features & Use Cases - Blocking scope challenge: Maps reusable existing code, flags plans touching 8+ files, and enforces 2-5 minute granularity per implementation leaf with decompose-or-accept decisions. - Four-section review: Covers architecture, code quality (DRY, error handling, tech debt), mandatory test coverage diagrams with regression rules, and performance (N+1 queries, caching, slow paths). - Persisted review report: Writes a REVIEW REPORT section with verdict into the plan doc and logs results via bin/li-review-log so the ship phase can gate on it. - Use Case: Before shipping a feature branch, run the review against your design doc to get a CLEAR/NOT CLEARED verdict, unresolved decision list, and a regression-test task list. ## Quick Start Ask the agent to run /plan-eng-review on your current plan document to produce a verdict and review report before 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 coding?▼

Run /plan-eng-review with an optional path to your plan or design doc; it auto-discovers design files if none is given. It performs a blocking scope challenge, then reviews architecture, code quality, tests, and performance, ending with a CLEAR or NOT CLEARED verdict.

What does the plan-eng-review skill check?▼

It checks architecture and data flow, DRY and error handling, test coverage via a mandatory coverage diagram, and performance issues like N+1 queries. It also enforces 2-5 minute task granularity, work-package boundaries, and cli_support/voice frontmatter on new skills.

Can I review a branch diff instead of a plan document?▼

Yes, pass --scope diff to review the current branch's changes instead of a plan doc. This degrades to lighter /review semantics while still applying the regression-test rule for modified behavior lacking coverage.

When should I not use an engineering plan review?▼

Skip it for trivial fixes like typos or comment changes where no plan exists, and for pure documentation PRs where the lighter /review skill is sufficient. It is designed as the required gate before non-trivial implementation and shipping.

What happens if the review report is missing before exiting plan mode?▼

The Exit Plan Mode gate blocks: the plan file must end with a REVIEW REPORT heading containing the status table and verdict, and the review log must have been written and read. Proceeding without it is treated as a contract violation.

Related Skills

Explore More Software Engineering Skills→
antriksh-29antriksh-29

office-hours

Draft structured design documents for startup ideas during office hours.

Community
Advanced
arbazkhan971arbazkhan971
26

ship

Automate shipping code changes with pre-ship checks, dry-run, execution, verification, and rollback.

Community
Advanced
Strat-Ai-Gize-Marketing-AutomationStrat-Ai-Gize-Marketing-Automation

onboarding-cro

Define activation events and design guided onboarding flows.

Official
Advanced
topoteretestopoteretes
30.4k

diff-risk-explainer

Explains what changed in small code diffs with brief summaries.

Official
Basic