plan-validation

bemgmt's avatarfrom bemgmt

Validate a plan or pipeline with evidence-based checks, dry runs, and research. Use when the user asks to validate, verify, or QA a plan or process or asks for confidence.

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

When & Why to Use This Skill

The Plan Validation skill empowers users to systematically verify the feasibility and reliability of complex plans or pipelines. By utilizing evidence-based checks, dry runs, and a structured validation matrix, it identifies potential risks and provides a data-driven confidence score to ensure successful execution and minimize failure rates.

Use Cases

  • Software Engineering: Validating deployment pipelines and CI/CD workflows through dry runs and evidence-based QA checks to prevent production errors.
  • Project Management: Auditing complex project roadmaps to identify hidden dependencies, resource blockers, and feasibility risks before the kickoff phase.
  • Data Operations: Verifying large-scale data migration or processing plans to ensure data integrity, environment permissions, and system compatibility.
  • Operational Strategy: Testing new business processes or SOPs against realistic success criteria and evidence to ensure they are actionable and scalable.
nameplan-validation
descriptionValidate a plan or pipeline with evidence-based checks, dry runs, and research. Use when the user asks to validate, verify, or QA a plan or process or asks for confidence.

Plan Validation

Overview

Turn a plan into a validation matrix and verify it with evidence.

Workflow

  1. Map each plan step to a validation method (test, dry run, sample, or metric).
  2. Identify required data, environments, and permissions.
  3. Run or propose minimal checks that prove feasibility early.
  4. Report confidence with supporting evidence and remaining risks.

Validation Matrix

  • Step
  • Validation method
  • Success criteria
  • Evidence or blockers

Output Rules

  • Provide a realistic confidence percentage with rationale.
  • Call out what is untested and what would change the confidence.
  • Separate evidence from assumptions and label unknowns explicitly.

Acceptance Criteria

  • Validation matrix is present and complete.
  • Confidence includes rationale and remaining unknowns.