plan-schema

To validate a plan file schema, apply the canonical reference to your markdown plan file to check required sections, naming conventions, and dependency graphs. This enforces correctness and reduces ambiguity in plan creation workflows.

A plan file schema provides a canonical reference for plan creation, enabling consistent templates, validation, and converter workflows. It defines the required sections and naming conventions that feed converters to generate prd.json and beads.

To convert a validated plan file to prd.json, use the converter mappings specified by the plan schema. The schema explains how plan files feed converters to generate prd.json and beads for downstream tooling.

Yes, the plan schema applies directly to plan editors, validators, and executors. It ensures interoperability across /plan-creator, /plan-loop, and related tools by enforcing consistent plan templates and dependency graphs.

The best way to enforce naming conventions in plan templates is to apply a canonical plan schema reference. It specifies required sections, naming conventions, and dependency graphs to enforce correctness and interoperability across tools.

Plan file validation fails during conversion when the file layout, required sections, or naming conventions do not match the canonical schema. Applying the schema ensures correct converter mappings and interoperability with downstream tools.