plan-eng-review

Identify gaps and risks in engineering plans across architecture, data flow, and test coverage.

2|Updated Dec 8, 2018
One-click install
npx skills add https://github.com/indykish/dotfiles --skill plan-eng-review-indykish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/indykish/dotfiles/tree/main/skills/plan-eng-review
Command: npx skills add https://github.com/indykish/dotfiles --skill plan-eng-review-indykish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng manager-mode plan review helps teams lock in execution plans by thoroughly analyzing architecture, data flow, diagrams, edge cases, test coverage, and performance, ensuring clarity before coding.

Core Features & Use Cases

  • Thorough plan review with opinionated recommendations and explicit tradeoffs.
  • ASCII diagram guidance and emphasis on maintainable scope and minimal diff.
  • Interactive questioning flow to gather input and solidify decisions before changes.

Quick Start

Review the current plan, outline architecture and data flow, surface edge cases and tests, then present an opinionated recommendation and request user input.

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 data flow gaps?

Engineering plan review identifies gaps and risks across architecture, data flow, and edge cases, then surfaces concrete tradeoffs and recommendations. It produces opinionated guidance, ASCII diagrams, and a concise scope decision to keep the plan focused.

What is the best way to surface tradeoffs and risks before coding begins?

The best way to surface tradeoffs is through an opinionated plan review that evaluates architecture, diagrams, edge cases, and test coverage. This process documents failure modes, dependencies, and testing implications to ensure clarity before implementation.

Can I use a guided question flow to solidify engineering decisions?

Yes, you can use a guided question flow to solidify engineering decisions. The review process interfaces with users by presenting 2-3 options at a time, gathering input to solidify decisions and outline maintainable scope before changes are made.

How do I document failure modes and testing implications for a software architecture?

To document failure modes and testing implications, apply an opinionated plan review that analyzes architecture and data flow. The review explicitly outlines dependencies, edge cases, and test coverage to produce concrete recommendations and minimal diff scope.

Does plan review help with maintaining minimal diff and manageable scope?

Plan review helps maintain minimal diff and manageable scope by producing a concise scope decision. It emphasizes maintainable scope through architecture analysis, ASCII diagram guidance, and explicit tradeoffs to keep the engineering plan focused.

How do I generate ASCII diagrams for engineering plan reviews?

To generate ASCII diagrams for engineering plan reviews, apply an opinionated review process that outlines architecture and data flow. The review produces ASCII diagram guidance alongside concrete recommendations to visualize system structure and maintain scope.