validate-plan-file

Name: validate-plan-file
Availability: InStock
Author: ronmikailov

Validate orchestrator plan files against the defined JSON schema.

Updated Aug 27, 2026

Search Tags:#validation #quality-assurance #orchestrator #software-engineering #json-schema #plan-validation

Ready to run

npx skills add https://github.com/ronmikailov/site-360 --skill validate-plan-file-ronmikailov

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: validate-plan-file
Source: https://github.com/ronmikailov/site-360/tree/main/.claude/skills/validate-plan-file
Command: npx skills add https://github.com/ronmikailov/site-360 --skill validate-plan-file-ronmikailov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrator plan files are created and consumed by multiple agents; malformed plan files can lead to downstream failures, misconfigurations, and unsafe behavior. This Skill validates plan content against the shared JSON schemas before processing.

Core Features & Use Cases

Schema-based validation across all plan types (bug, security, dead-code, dependency) with base and domain-specific checks.
Detailed error reporting and schema loading to guide quick remediation.
Use Case: validate a newly created plan file at commit time or prior to deployment to prevent runtime errors in workers.

Quick Start

Provide the path to a plan file and run the validate-plan-file skill to verify its schema.

Frequently Asked Questions about validate-plan-file

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

FAQPage Schema

How do I validate orchestrator plan files against a JSON schema?▼

Validating orchestrator plan files against a JSON schema requires checking base and domain-specific constraints to prevent malformed inputs. This skill applies validation at creation or before workers read them, covering bug, security, dead-code, and dependency workflows.

What is the best way to prevent malformed orchestrator plans from causing downstream failures?▼

Preventing downstream failures from malformed orchestrator plans requires schema-based validation before processing. By validating plan content against shared JSON schemas, you catch misconfigurations and unsafe behavior early at commit time or prior to deployment.

Can I use JSON schema validation for different orchestrator plan types like bug and security workflows?▼

JSON schema validation supports all orchestrator plan types, including bug, security, dead-code, and dependency workflows. It enforces both base and domain-specific checks to ensure plans meet required structural and contextual constraints.

How do I get detailed error reporting for orchestrator plan validation issues?▼

Detailed error reporting for orchestrator plan validation issues is generated automatically when schema loading and checks are applied. This reporting guides quick remediation by pinpointing exactly where and how a plan file violates defined constraints.

When do I need to validate orchestrator plan files in the software engineering lifecycle?▼

Validating orchestrator plan files is needed at creation or commit time, and before workers read them. This prevents runtime errors and ensures workers only consume structurally sound, schema-compliant plans in relevant environments.

Does orchestrator plan validation work without external dependencies?▼

Orchestrator plan validation works without external dependencies, relying solely on defined JSON schemas and internal loading mechanisms. It applies base and domain-specific constraints independently to verify plan files.