review-plan

Review complex project plans with mode-driven analysis and structured risk mapping.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill review-plan-indigoai-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-plan
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/review-plan
Command: npx skills add https://github.com/indigoai-us/hq --skill review-plan-indigoai-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review planning at scale by enforcing a disciplined, mode-driven evaluation workflow to raise plan quality and surface risks early.

Core Features & Use Cases

  • Mode-driven reviews (EXPANSION, SELECTIVE EXPANSION, HOLD, REDUCTION) to determine scope, ambition, and trade-offs.
  • Systematic risk analysis, data-flow scrutiny, and observability planning to strengthen plans before execution.
  • Structured guidance for architecture, security, deployment readiness, and long-term trajectory across product, engineering, and operations.

Quick Start

Execute a full plan review in EXPANSION mode on the provided proposal and generate a detailed risk map, delegation plan, and rollout trajectory.

Frequently Asked Questions about review-plan

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

FAQPage Schema
How do I conduct a rigorous project plan review for a complex PRD?

Project plan review evaluates multi-section proposals and roadmaps using mode-driven analysis to identify risks, map data flows, and strengthen deployment readiness. It systematically critiques scope, security, and long-term trajectory to increase plan quality.

What is mode-driven evaluation in product and engineering roadmap reviews?

Mode-driven evaluation guides plan reviews by applying EXPANSION, SELECTIVE EXPANSION, HOLD, or REDUCTION modes to determine scope, ambition, and trade-offs. This mechanism structures the analysis of risk, system audit, and rollout trajectory across product and engineering plans.

How to perform threat modeling and risk analysis on a system architecture proposal?

Risk analysis on architecture proposals applies systematic scrutiny to data flows, security, and observability planning. By mapping errors and evaluating deployment readiness, the review surfaces threats early and strengthens the plan before execution begins.

Can I use this system audit workflow for operational plans and deployment readiness checks?

Yes, the system audit workflow applies to operational plans, product proposals, and engineering roadmaps. It evaluates deployment readiness and long-term trajectory by enforcing disciplined, mode-driven reviews tailored to the specific scale and context of your rollout.

What is the best way to review a multi-section proposal when scope and rollout are at stake?

Reviewing multi-section proposals with the most at stake requires disciplined, mode-driven evaluation to surface risks early and map deployment trajectories. This approach ensures structured guidance across architecture, security, and observability before execution.

When should I not use a full EXPANSION mode review for my project roadmap?

You should avoid EXPANSION mode when project scope or rollout trajectory indicates a need to limit ambition. If risk analysis or system audit reveals significant constraints, switching to HOLD or REDUCTION modes provides a safer evaluation framework for your plan.