plan-review

Evaluate feature plans across strategy, design, and engineering to identify gaps.

60|9|Updated Apr 1, 2026

Search Tags:#requirements #product-management #risk-analysis #plan-review #feature-design #engineering-feasibility

Ready to run

npx skills add https://github.com/mvschwarz/openrig --skill plan-review-mvschwarz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/mvschwarz/openrig/tree/main/packages/daemon/specs/agents/shared/skills/pm/plan-review
Command: npx skills add https://github.com/mvschwarz/openrig --skill plan-review-mvschwarz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Organizations often build features that drift from strategy, neglect user needs, or reveal engineering risks. This skill provides a multi-perspective review to catch gaps before development starts, aligning plans with objectives and feasibility.

Core Features & Use Cases

Three review lenses: Strategy (business goals and opportunity fit), Design (UX and accessibility), and Engineering Feasibility (specification clarity and technical considerations).
Stepwise process: read material, run all three reviews, synthesize findings, and generate an executive summary.
Use Case: before committing to a feature, perform a plan review to surface missing requirements and alignment issues that could affect delivery.

Quick Start

Input the feature requirements document and run the three review lenses to identify gaps, risks, and opportunities.

Frequently Asked Questions about plan-review

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

FAQPage Schema

How do I review feature plans to catch gaps before development starts?▼

To review feature plans, evaluate requirements across strategy, design, and engineering lenses to identify gaps and misalignments early. This structured plan review process synthesizes cross-disciplinary findings into an executive summary to align plans with business goals and feasibility before committing to development.

What is a multi-perspective plan review for product management?▼

A multi-perspective plan review assesses feature requirements through three lenses: strategy for business opportunity fit, design for UX and accessibility, and engineering feasibility for specification clarity. It catches missing requirements and alignment issues by applying cross-disciplinary input during early-stage planning workflows.

How do I assess engineering feasibility and design risks in a feature plan?▼

Assess engineering feasibility and design risks by running structured review lenses on the feature requirements document. The engineering lens checks specification clarity and technical considerations, while the design lens evaluates UX and accessibility, synthesizing these findings to surface potential delivery risks.

When do I need to perform a structured plan review in the development lifecycle?▼

You need a structured plan review during early-stage planning workflows before committing to feature development. Perform this review when requirements are evolving and cross-disciplinary input is needed to surface missing requirements, ensuring the plan aligns with objectives and technical feasibility before resources are allocated.

Can I use this plan review for early-stage requirements that are still evolving?▼

Yes, this plan review is specifically designed for early-stage planning workflows where requirements evolve. It reads your current material, runs strategy, design, and engineering assessments, and synthesizes gaps to support cross-disciplinary alignment even when the feature specifications are not yet finalized.

What is the best way to align feature design with business strategy before building?▼

The best way to align feature design with strategy is applying a three-lens review that evaluates business goals, UX accessibility, and engineering feasibility. This synthesizes cross-disciplinary findings into an executive summary, catching misalignments between the feature plan and overarching business objectives early.