skills.rest
jyang234
jyang234COMMUNITY
Explore all skills by this author →
GitHub

plan-review

Analyze architectural plans for regression risk, complexity, and over-engineering.

Updated Jan 30, 2026
Search Tags:#architecture#complexity#risk-assessment#design-review#plan-review#regression-risk
One-click install
npx skills add https://github.com/jyang234/ai-engineering-framework --skill plan-review-jyang234
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/jyang234/ai-engineering-framework/tree/main/edi/internal/assets/skills/plan-review
Command: npx skills add https://github.com/jyang234/ai-engineering-framework --skill plan-review-jyang234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes architectural plans to identify regression risk, unnecessary complexity, and over-engineering early in the design process, helping teams avoid costly redesigns.

Core Features & Use Cases

  • Phase 1: RECALL Context Loading
  • Phase 2: Regression Risk Assessment
  • Phase 3: Complexity Assessment
  • Phase 4: Over-Engineering Detection (YAGNI)
  • Phase 5: Structured Output
  • Use Case: Pre-implementation plan reviews to catch issues before coding starts.

Quick Start

Trigger the plan-review on your current architecture draft to generate a risk-focused evaluation and concrete recommendations.

Frequently Asked Questions about plan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review architectural plans for regression risk before implementation?▼

Regression risk assessment examines how proposed changes could break existing functionality. Plan-review analyzes blast radius, past failures, test coverage, and rollback strategies to identify vulnerabilities early, preventing costly failures after deployment.

What's the best way to detect unnecessary complexity and over-engineering in design?▼

Over-engineering detection applies YAGNI (You Aren't Gonna Need It) principles to spot redundant features and over-abstraction. Plan-review flags these during early design phases so teams can simplify before coding starts.

When should I conduct a design review to catch issues early?▼

Design reviews are most effective during early design phases, before implementation begins. Plan-review produces structured risk summaries and complexity assessments at this stage, enabling course correction without rework.

How do I assess whether a proposed architecture change has adequate test coverage and rollback strategy?▼

Plan-review evaluates test coverage and rollback readiness as core components of regression risk assessment. Missing elements are identified in structured output, highlighting gaps before deployment risk becomes real.

Can I use plan review to identify missing safety measures in my architecture?▼

Yes. Plan-review produces a verdict that includes missing elements—gaps in testing, monitoring, or fallback logic. The structured output flags what's absent so teams address vulnerabilities proactively.

Related Skills

Explore More Software Engineering Skills→
dralgorhythmdralgorhythm
111

designing-systems

Design scalable software systems with C4 diagrams and trade-off analysis.

Community
Advanced
lucasloutayflucasloutayf

shipping-and-launch

Plan and execute production launches with staged rollouts and rollback procedures.

Community
Advanced
proffesor-for-testingproffesor-for-testing
436

chaos-engineering-resilience

Inject controlled failures into distributed systems to test resilience and recovery.

Community
Advanced
saifoellohsaifoelloh
16

golang-best-practices

Automate Go code reviews for anti-patterns across five specialized domains.

Community
Advanced