plan-eng-review

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

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kadenn/kstack --skill plan-eng-review-kadenn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/kadenn/kstack/tree/main/plan-eng-review
Command: npx skills add https://github.com/kadenn/kstack --skill plan-eng-review-kadenn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng managers need a structured, opinionated way to validate and lock in execution plans; plan-eng-review guides interactive reviews that cover architecture, data flow, edge cases, tests, and performance.

Core Features & Use Cases

  • Interactive review to surface tradeoffs, provide recommendations, and finalize the plan.
  • ASCII diagrams and explicit data-flow representations to communicate design decisions.
  • Alignment guidance for sprint planning, architecture reviews, and feature rollouts with clear documentation.

Quick Start

Describe the feature to ship and run a plan-eng-review to lock in architecture, data flow, and tests.

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 architecture and data flow?

An engineering plan review validates architecture and data flow by surfacing tradeoffs and generating ASCII diagrams. It enforces prioritization and covers edge cases and tests to finalize execution strategies with clear, opinionated documentation.

What is the best way to lock in execution strategies for feature rollouts?

Locking in execution strategies requires structured plan reviews that provide opinionated recommendations and actionable artifacts. Sprint planning and feature rollouts benefit from explicit tradeoff documentation and test coverage alignment.

Can I generate ASCII diagrams during an architecture review?

Yes, architecture reviews can generate ASCII diagrams to communicate explicit data-flow representations and design decisions. These diagrams serve as actionable artifacts that align teams during sprint planning and feature rollouts.

Does a structured plan review help with edge cases and test coverage?

Structured plan reviews explicitly address edge cases and test coverage by enforcing prioritization and providing opinionated recommendations. This ensures teams document tradeoffs and finalize architecture plans with comprehensive test alignment.

When do I need an opinionated engineering plan review?

You need an opinionated engineering plan review when teams require explicit tradeoffs, documentation, and test coverage for sprint planning or architecture reviews. It finalizes design decisions through interactive alignment and actionable artifacts.