plan-eng-review

Review complex design and engineering plans for risks and tradeoffs.

2|Updated Feb 9, 2026

Search Tags:#architecture #decision-making #risk-analysis #plan-review #engineering-management #ASCII-diagrams

Ready to run

npx skills add https://github.com/madebynoam/bryllen --skill plan-eng-review-madebynoam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/madebynoam/bryllen/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/madebynoam/bryllen --skill plan-eng-review-madebynoam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a disciplined, interactive plan-review workflow that surfaces risks, trade-offs, and action items for complex projects.

Core Features & Use Cases

Guided, factorized decision points with structured option sets.
ASCII diagrams and artifacts to document architecture, risk, and test plans.
Iterative plan refinement across architecture, implementation, and testing.

Quick Start

Start a plan review on your current project, answer the guided questions, and iterate until you reach a final, actionable plan.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema

How do I conduct an engineering plan review for complex architecture decisions?▼

Engineering plan reviews require a structured workflow that surfaces risks and trade-offs. This approach uses guided questions and ASCII diagrams to evaluate architecture, code quality, testing, and performance scenarios, producing actionable documentation for multi-team projects.

What is the best way to document risk analysis and trade-offs in software design?▼

Documenting risk analysis in software design involves creating structured artifacts like architecture notes and TODOs. Using a factorized decision-making process with visual aids such as ASCII diagrams helps capture options and guides execution across engineering teams.

How does interactive plan refinement work for multi-team engineering projects?▼

Interactive plan refinement uses an AskUserQuestion-driven dialogue to iteratively evaluate implementation and testing phases. This structured method progressively narrows down architectural options and surfaces action items until a final, actionable engineering plan is reached.

Can I use ASCII diagrams for visualizing architecture and test plans during a plan review?▼

Yes, ASCII diagrams are used to visually document architecture, risk analysis, and test plans during the review. They provide clear, text-based visual aids that help engineering teams understand complex system structures and factorized decision points.

When do I need a structured workflow for architecture and code quality reviews?▼

You need a structured workflow for architecture and code quality reviews when managing complex, multi-team engineering projects. A disciplined plan-review process is essential to systematically surface risks, evaluate trade-offs, and document decisions before implementation begins.

What are the limitations of using guided questions for engineering risk analysis?▼

Guided questions for engineering risk analysis depend heavily on accurate user input during the AskUserQuestion-driven dialogue. The approach requires active participation to iterate through architecture and testing phases, meaning incomplete answers may limit the depth of the resulting risk analysis and action items.