plan-eng-review

Analyze architecture plans and execution steps to identify gaps and risks.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill plan-eng-review-amanik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack/plan-eng-review
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill plan-eng-review-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eng managers and teams often struggle to converge on a concrete execution plan for architecture, data flow, and edge cases before starting implementation. This Skill guides interactive reviews to lock in plans, diagrams, and acceptance criteria so engineers can code with fewer rework cycles.

Core Features & Use Cases

  • Interactive architecture reviews that surface risks, edge cases, and trade-offs.
  • Guidance on data flow diagrams, test coverage planning, and performance considerations.
  • Proactive recommendations for plan improvements when a plan or design doc is present or about to start coding.

Quick Start

Review the current engineering plan and lock in the execution path, data flows, and testing strategy before implementation.

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 architecture plan to identify gaps and risks before coding?

Review an architecture plan by analyzing proposed execution steps, data flows, and edge cases to identify gaps and risks. This interactive process surfaces trade-offs, tests coverage considerations, and aligns the design with business goals to lock in a concrete execution path.

What is the best way to align data flow diagrams and test coverage with business goals?

The best way to align data flow diagrams and test coverage with business goals is through an interactive architecture review. This process evaluates your proposed execution steps, proactively surfacing risks and providing actionable recommendations for plan improvements.

Can I use an architecture review to catch edge cases and performance considerations in my design doc?

Yes, you can use an architecture review to catch edge cases and performance considerations. By analyzing your design doc before implementation, the review identifies potential gaps, evaluates trade-offs, and provides a concrete plan for next steps with full justification.

How do I lock in execution plans and acceptance criteria to reduce engineering rework cycles?

Lock in execution plans and acceptance criteria by conducting interactive reviews that compare proposed architecture steps against business goals. This proactive analysis identifies risks and trade-offs early, ensuring engineers can code with fewer rework cycles.

Does this architecture design review work for teams that are about to start coding?

Yes, this architecture design review is ideal for teams about to start coding. It provides proactive recommendations for plan improvements when a design doc is present, ensuring execution paths, data flows, and testing strategies are locked in before implementation begins.

What are the limitations of running an architecture review without a concrete execution plan?

Without a concrete execution plan, an architecture review cannot effectively compare proposed steps or identify specific gaps in data flow and test coverage. The review requires a present or proposed design doc to provide actionable recommendations and a justified plan for next steps.