plan-eng-review

Review engineering plans for architecture, data flow, edge cases, and test coverage.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill plan-eng-review-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/plan-eng-review
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill plan-eng-review-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lock in architecture decisions, data flow, edge cases, and test coverage during engineering planning.

Core Features & Use Cases

  • Interactive engineering plan review that surfaces risks, tradeoffs, and acceptance criteria.
  • Proactive planning for design reviews, architecture walkthroughs, and system evaluations before coding.
  • Guidance to identify missing diagrams, tests, or performance considerations and to propose actionable next steps.

Quick Start

Provide a design brief or plan and run a structured architecture review covering scope, data flow, edge cases, tests, and risk.

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 before coding?

To review an architecture plan, provide a design brief to evaluate scope, data flow, edge cases, and test coverage. This structured engineering review surfaces risks, tradeoffs, and acceptance criteria, producing an actionable plan with recommended next steps.

What is an engineering design review and when do I need it?

An engineering design review is a proactive planning process for locking in architecture decisions before coding. You need it during architecture walkthroughs or system evaluations to identify missing diagrams, tests, or performance considerations early.

How do I assess risks and edge cases in a system design document?

Assess risks and edge cases in a system design document by running a structured architecture review. This process evaluates data flow and test coverage against your design brief, highlighting tradeoffs and missing performance considerations.

Can I use an architecture walkthrough to identify missing test coverage?

Yes, an architecture walkthrough identifies missing test coverage by evaluating your design brief against acceptance criteria. The review process proactively checks for missing tests, diagrams, and performance considerations before coding begins.

What is the best way to lock in architecture decisions during planning?

The best way to lock in architecture decisions is conducting an interactive engineering plan review. It evaluates your design brief to surface tradeoffs and acceptance criteria, outputting an actionable plan with risk assessment and recommended next steps.