skills.rest
AkbarDevop
AkbarDevopCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-eng-review

Analyze engineering plans to produce architecture, failure modes, and test plans.

Updated Mar 12, 2026
Search Tags:#architecture#engineering#risk-management#data-flow#plan-review#ascii-diagrams
One-click install
npx skills add https://github.com/AkbarDevop/gstack-codex --skill plan-eng-review-akbardevop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/AkbarDevop/gstack-codex/tree/main/plan-eng-review
Command: npx skills add https://github.com/AkbarDevop/gstack-codex --skill plan-eng-review-akbardevop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock in execution plans for engineering work by thoroughly reviewing architecture, data flows, edge cases, test coverage, and performance requirements to reduce rework and risk.

Core Features & Use Cases

  • Interactive architecture review with trade-off analysis and ASCII diagrams.
  • Data-flow mapping for visibility into dependencies, bottlenecks, and failure modes.
  • Step 0 Scope Challenge to constrain scope before starting work.

Quick Start

Describe a feature and I will provide an engineering plan review with architecture and risk assessment.

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 for architecture and risk management?▼

Engineering plan reviews analyze architecture, data flows, and failure modes to produce test plans and trade-off recommendations. This structured review process evaluates scope, dependencies, and performance requirements to reduce rework and risk before execution.

What is a Step 0 Scope Challenge in feature development planning?▼

A Step 0 Scope Challenge constrains project scope before starting engineering work by questioning requirements early. This pre-planning mechanism limits unnecessary features and focuses architecture decisions on essential system-level design elements.

How do I map data flows to identify bottlenecks and failure modes?▼

Data-flow mapping visualizes dependencies and system interactions to pinpoint bottlenecks and failure modes. Creating ASCII diagrams during architecture review clarifies system behavior and highlights performance constraints across engineering plans.

Can I use ASCII diagrams for system-level design decisions and refactoring?▼

ASCII diagrams support system-level design decisions, new feature planning, and refactoring by visually representing architecture and data flows. They provide lightweight, text-based visualizations for mapping dependencies and trade-off analysis during plan reviews.

What should be included in test plans and acceptance criteria for an engineering plan review?▼

Engineering plan reviews generate test plans with acceptance criteria covering edge cases, performance requirements, and failure modes. Recommended trade-offs define specific validation thresholds to ensure architecture meets scope and quality standards.

When do I need architecture trade-off analysis for a new feature?▼

Architecture trade-off analysis is needed when new features or refactors impact system dependencies, data flows, or performance constraints. Structured plan reviews evaluate these trade-offs against acceptance criteria to mitigate risk and reduce rework.

Related Skills

Explore More Software Engineering Skills→
TienchingTienching
3

ralph-init

Generate a canonical PRD and initialize Ralph progress tracking.

Community
Intermediate
henrybravohenrybravo

implementation-planning

Create implementation plans with Mermaid diagrams and acceptance criteria.

Community
Advanced
JaviMontanoJaviMontano

apex-dependency-mapping

Identify, classify, and visualize inter-project dependencies across a portfolio.

Community
Advanced
thucpruthucpru

planning

Plan scalable technical solutions with implementation plans and trade-off analysis.

Community
Advanced