skills.rest
AskTinNguyen
AskTinNguyenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-eng-review

Review engineering plans for scope, risks, and design decisions.

1|Updated Jan 26, 2026
Search Tags:#planning#architecture#engineering#risk-management#code-review#ascii-diagrams
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill plan-eng-review-asktinnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/gstack/plan-eng-review
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill plan-eng-review-asktinnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and reviewing engineering changes with a structured, opinionated plan to lock in architecture, data flow, diagrams, edge cases, tests, and performance before coding.

Core Features & Use Cases

  • Step-zero: Scope Challenge to establish minimal viable change and cut scope.
  • ASCII diagram emphasis: Use ASCII diagrams for data flow, state machines, and pipelines in plans and docs.
  • Decision points: Each plan includes explicit recommendations and tradeoffs to guide stakeholders.

Quick Start

Provide a scoped engineering plan review and follow the four review sections in sequence.

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 plan before implementation to identify architectural risks?▼

To review an engineering plan, apply a structured workflow that surfaces scope, risks, and design decisions across architecture, code quality, tests, and performance sections before coding begins.

What is the best way to structure a software architecture review using ASCII diagrams?▼

Structure an architecture review by using ASCII diagrams to map data flow, state machines, and pipelines, guided by structured questions that enforce explicit decision tradeoffs.

How do I challenge scope and establish minimal viable change in a software project plan?▼

Challenge scope by running a Step-Zero Scope Challenge to establish the minimal viable change, cut unnecessary features, and lock in architecture before the implementation phase starts.

Does this engineering plan review workflow cover code quality and performance considerations?▼

Yes, the engineering plan review workflow covers code quality and performance considerations, alongside architecture and tests, using four structured review sections to guide stakeholder decisions.

How do I configure scope and decision criteria for an architecture review?▼

Configure scope and decision criteria for an architecture review using a front-matter driven configuration that enforces structured inputs before evaluating the four review sections.

When should I not use an opinionated engineering plan review workflow?▼

Avoid using an opinionated engineering plan review workflow for rapid prototyping or trivial changes where a full scope challenge, ASCII diagramming, and structured tradeoff analysis would add unnecessary overhead.

Related Skills

Explore More Software Engineering Skills→
GrimblazGrimblaz
3

design-exploration

Structure design decision problems and define user goals to surface viable options.

Community
Advanced
normcrandallnormcrandall
1

Quality Assurance

Validates implemented software stories with tests, code review, and quality gate assessment.

Community
Basic
PedroGiudicePedroGiudice
5

architecture-diagram-creator

Generate HTML architecture diagrams with data flows and deployment layers.

Community
Advanced
ssv445ssv445
1

plan-exit-review

Review plans for scope, architecture, and quality gates with actionable recommendations.

Community
Advanced