plan-audit

Audit or critique a plan for feasibility, risks, missing steps, and test coverage. Use when the user asks to review, audit, or critique a plan or process.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

The Plan Audit skill is a specialized analytical tool designed to rigorously evaluate project plans and operational processes for feasibility, potential risks, and missing steps. It provides a structured critique by identifying gaps in dependencies, security, and test coverage, ensuring that every phase of a project is validated and actionable. By grouping findings by severity and offering specific fixes, it helps teams mitigate risks and optimize workflows before execution begins.

Use Cases

  • Technical Roadmap Review: Critiquing a software development plan to identify missing architectural dependencies, data migration risks, and insufficient unit test coverage.
  • Operational Process Auditing: Evaluating a new business SOP to ensure all necessary approvals, access requirements, and safety guardrails are documented and feasible.
  • Risk Mitigation in Project Planning: Analyzing a project timeline to flag high-risk assumptions, potential cost overruns, and security vulnerabilities before the execution phase.
  • Deployment Readiness Assessment: Auditing a system rollout plan for rollback strategies, performance monitoring metrics, and acceptance criteria to ensure a smooth transition.
nameplan-audit
descriptionAudit or critique a plan for feasibility, risks, missing steps, and test coverage. Use when the user asks to review, audit, or critique a plan or process.

Plan Audit

Overview

Evaluate a proposed plan for gaps, risks, and weak validation.

Workflow

  1. Restate the plan scope and goals to confirm alignment.
  2. Check for missing steps: dependencies, data migrations, access, approvals, or rollback.
  3. Evaluate risks: security, privacy, performance, cost, and maintainability.
  4. Assess validation: tests, metrics, and acceptance criteria for each step.
  5. Provide fixes: add steps, reorder, or split into phases.

Audit Output

  • Findings grouped by severity: critical, major, minor.
  • For each finding, include impact and the recommended change.
  • Note any assumptions that need confirmation.

Honesty Guardrails

  • Flag evidence gaps and avoid implying verification that did not happen.
  • Provide confidence notes for high-risk claims.

Acceptance Criteria

  • Findings are grouped by severity with impact and fix.
  • Assumptions and evidence gaps are explicit.