plan-eng-review

Review software engineering plans for architecture, code quality, testing, and performance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers review their software engineering plans by ensuring architectural soundness, code quality, thorough testing, and optimal performance, providing recommendations and insights for improvements.

Core Features & Use Cases

  • Architecture Review: Evaluates system design, component boundaries, dependency graph, data flow, and scalability.
  • Code Quality: Checks code organization, DRY principles, error handling, and technical debt.
  • Testing: Inspects test coverage, edge case handling, mocking, and stubbing strategies.
  • Performance: Identifies potential bottlenecks in queries, memory usage, caching, and slow code paths.
  • Use Case: After finalizing a plan for a new project or feature, this Skill helps in catching potential issues early before implementation.

Quick Start

Run the engineering review on your design doc to ensure comprehensive planning and quality control.

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 a software engineering plan for architecture and code quality?

Thoroughly reviewing a software engineering plan involves evaluating system design, component boundaries, data flow, and code organization. This ensures architectural soundness, verifies DRY principles, and identifies technical debt before implementation begins.

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

An engineering review is a comprehensive evaluation of a project's design, testing strategies, and performance optimizations. You need it after finalizing a plan for a new feature to catch potential issues early before implementation starts.

How do I identify performance bottlenecks and testing gaps in my system design?

Identifying performance bottlenecks and testing gaps requires inspecting slow code paths, memory usage, caching, and database queries. You must also analyze test coverage, edge case handling, and mocking strategies to ensure comprehensive quality control.

Can I use an architectural review to check scalability and dependency graphs?

Yes, an architectural review evaluates system design, component boundaries, dependency graphs, and data flow to ensure scalability. It provides actionable recommendations and insights for improving architectural soundness and overall system design quality.

What's the best way to catch technical debt and security issues before implementation?

The best way to catch technical debt and security issues is to run an in-depth review of your finalized engineering plan. This requires expertise in software design principles and best practices to identify potential problems early in the development lifecycle.