One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill plan-review-expert
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-review-expert
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/plan-review-expert
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill plan-review-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Plan Review Expert prevents failed implementations by systematically checking whether an engineering plan is complete, safe, and realistically achievable before work begins.

Core Features & Use Cases

  • Completeness verification: Detects missing requirements, absent edge cases, and uncovered critical steps in technical proposals.
  • Risk identification: Surfaces technical, security, scalability, and maintainability issues with concrete severities and mitigations.
  • Dependency and alternative analysis: Checks step ordering, blocking dependencies, and encourages comparing alternative approaches to reduce architectural risk.
  • Security threat checklist: Reviews plans using a structured model (e.g., spoofing, tampering, authorization, rate limiting) to ensure critical security controls are explicitly covered.

Quick Start

Use plan-review-expert when you are reviewing an implementation plan for a feature or design document and want a structured verdict, missing sections, and actionable fixes.

Frequently Asked Questions about plan-review-expert

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

FAQPage Schema
How do I review an implementation plan for missing requirements and security gaps?▼

Review an implementation plan by systematically checking for completeness, security threats, dependencies, and scalability. This process identifies missing requirements, surfaces technical risks with mitigations, and produces a structured verdict to prevent failed implementations before coding begins.

What is the best way to validate a technical proposal before development starts?▼

Validating a technical proposal requires a structured architecture review that checks step ordering, blocking dependencies, and alternative approaches. This method ensures the design is realistically achievable by producing a detailed risk assessment with concrete severities and recommended fixes.

Does my feature plan cover critical security controls like spoofing and tampering?▼

To determine if your feature plan covers security controls, apply a structured threat checklist reviewing spoofing, tampering, authorization, and rate limiting. This validates that critical security measures are explicitly addressed and surfaces any absent controls before implementation.

How to assess technical risks and dependency ordering in a design document?▼

Assess technical risks in a design document by analyzing dependency chains, verifying step ordering, and evaluating maintainability issues. This risk identification process outputs structured risk items with concrete severities and actionable mitigations to reduce architectural vulnerabilities.

When do I need a structured plan review for my software engineering project?▼

You need a structured plan review when validating the completeness, error handling, and scalability of a technical proposal or feature plan before implementation. This process detects missing edge cases and uncovered critical steps, ensuring the plan is safe and realistically achievable.