validate-plan

Validate blocked implementation plans using logic-validator and external reviews.

9|Updated Aug 20, 2018
One-click install
npx skills add https://github.com/berlysia/dotfiles --skill validate-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-plan
Source: https://github.com/berlysia/dotfiles/tree/main/.skills/validate-plan
Command: npx skills add https://github.com/berlysia/dotfiles --skill validate-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure that a Plan Mode plan is logically sound and ready for implementation by running a structured validation workflow that may involve a logic-validator and optional external reviews.

Core Features & Use Cases

  • Logic validation: Verifies the consistency and completeness of the plan's steps using a dedicated logic validator.
  • External review orchestration: Optionally invokes codex-review or self-review for deeper assessment when needed.
  • Validation gating: Ensures that a plan is marked with <!-- validated --> before ExitPlanMode proceeds to implementation or rework.

Quick Start

Run the validation after ExitPlanMode is blocked to start the validation cycle, review results, and annotate the plan with the validation marker if it passes.

Frequently Asked Questions about validate-plan

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

FAQPage Schema
How do I validate an implementation plan after ExitPlanMode is blocked?

To validate an implementation plan after ExitPlanMode is blocked, trigger the validation workflow to check step consistency using a logic-validator and optionally invoke external reviews before proceeding to implementation.

What is plan validation and when do I need it?

Plan validation is the structured process of verifying logical consistency and completeness of implementation steps. You need it when a plan is blocked to ensure it is ready for implementation or requires rework.

Can I use external reviews to check my plan before implementation?

Yes, you can orchestrate external reviews using codex-review or self-review for deeper assessment. This validates plan quality across stages before deciding to proceed to implementation or revise.

How does a validated plan get marked for implementation?

A validated plan gets marked by enforcing a specific marker, <!-- validated -->, on success. This annotation gates the ExitPlanMode process, guiding whether to proceed to implementation or revise the plan.

What is the best way to ensure plan quality across multiple stages?

The best way to ensure plan quality is running a structured validation workflow that applies logic validation and optional external reviews, enforcing a validation marker before proceeding to implementation.

Why does my plan get blocked before implementation?

Your plan gets blocked by a hook before implementation to trigger a mandatory validation cycle. This ensures the plan's logic is sound and marked with <!-- validated --> before any implementation begins.