plan-reviewer

Analyze development plans for risks, gaps, and dependencies before implementation.

1|3|Updated Feb 28, 2026

Search Tags:#architecture #dependencies #compliance #risk-analysis #security-review #plan-review

Ready to run

npx skills add https://github.com/vobbilis/aigile --skill plan-reviewer-vobbilis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-reviewer
Source: https://github.com/vobbilis/aigile/tree/main/.github/skills/plan-reviewer
Command: npx skills add https://github.com/vobbilis/aigile --skill plan-reviewer-vobbilis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured framework to review high-risk development plans before implementation, catching critical gaps and risks early.

Core Features & Use Cases

Mandatory for migrations, authentication/authorization changes, third-party integrations, architecture changes, and breaking API changes.
Provides a step-by-step review process (UNDERSTAND, RESEARCH, ANALYZE, REPORT) and a checklist across authentication, database, API, and dependencies.
Supports evidence-based reporting and actionable recommendations to prevent costly failures.

Quick Start

Begin by outlining the plan goal, then use the standard checklist to assess risks, dependencies, and potential gaps.

Frequently Asked Questions about plan-reviewer

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

FAQPage Schema

How do I review an architecture migration plan for security and compliance risks?▼

To review an architecture migration plan for security and compliance risks, you need a structured checklist assessing authentication, database, API, and dependency gaps. This process identifies critical risks early and provides evidence-based mitigations before implementation begins.

What is the best way to analyze a development plan for third-party integration dependencies?▼

The best way to analyze a development plan for third-party integration dependencies is following a structured UNDERSTAND, RESEARCH, ANALYZE, and REPORT process. This framework ensures you document all dependencies and potential gaps across your tech stack before implementation.

When do I need a formal risk analysis for breaking API changes?▼

You need a formal risk analysis for breaking API changes whenever you shift architecture, alter authentication, or integrate external services. A documented checklist review catches critical gaps and dependencies early, preventing costly implementation failures across any tech stack.

Can I use this plan review process for auth changes across any tech stack?▼

Yes, you can use this plan review process for auth changes across any tech stack. It applies a standard checklist to assess authentication, database, API, and dependency risks, ensuring evidence-based reporting and actionable recommendations regardless of your specific technologies.

What steps should I follow to assess gaps in a database migration plan?▼

To assess gaps in a database migration plan, follow the step-by-step review process: UNDERSTAND the goal, RESEARCH the impact, ANALYZE risks using a standard checklist, and REPORT findings. This yields documented risk assessments and recommended mitigations.