eng-review

Automate structured engineering plan reviews covering architecture, data flow, and risks.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/norbert-pap/claudebert --skill eng-review-norbert-pap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eng-review
Source: https://github.com/norbert-pap/claudebert/tree/main/eng-review
Command: npx skills add https://github.com/norbert-pap/claudebert --skill eng-review-norbert-pap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, opinionated framework to review engineering plans, ensuring clear decisions on architecture, data flow, diagrams, edge cases, test coverage, and performance.

Core Features & Use Cases

  • Guided, deterministic plan review prompts that cover architecture, data flow, and validation checkpoints.
  • ASCII diagrams and narratives to convey state machines, pipelines, and dependencies.
  • Comprehensive risk assessment with recommendations and trade-off analysis.
  • Documentation of edge cases, test plans, and performance considerations for release readiness.

Quick Start

Initiate eng-review on the current project to start a structured, opinionated plan review.

Frequently Asked Questions about eng-review

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

FAQPage Schema
How do I review an engineering plan for architecture and data flow risks?

Engineering plan reviews validate architecture and data flow by applying structured prompts that confirm risk considerations, edge cases, and test coverage. This process generates ASCII diagrams, state descriptions, and actionable recommendations to ensure release readiness.

What should an engineering plan review cover before release?

A thorough engineering plan review must cover architecture decisions, data flow validation, edge case documentation, test coverage enforcement, and performance considerations. It produces trade-off analyses and actionable recommendations to confirm complete release readiness.

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

During an engineering plan review, ASCII diagrams for state machines and pipelines are generated through deterministic, prompt-driven workflows. These diagrams visualize dependencies and state descriptions to convey architecture and data flow narratives.

Can I use a structured review process for feature-level engineering plans?

Structured engineering plan reviews apply across software projects and feature scopes. They execute a deterministic workflow that enforces test coverage and performance checks regardless of the project's scale or feature boundaries.

What is the best way to enforce test coverage and performance considerations in a plan review?

The best way to enforce test coverage and performance considerations is through an opinionated, prompt-driven engineering plan review. This deterministic workflow validates architecture and generates actionable recommendations while checking release readiness.

Why does my engineering plan review miss edge cases and trade-off analysis?

Engineering plan reviews miss edge cases and trade-off analysis when lacking a structured, opinionated framework. A complete review requires deterministic prompts that enforce risk assessment, state descriptions, and comprehensive validation checkpoints.