plan-schema

Name: plan-schema
Availability: InStock
Author: GantisStorm

Define canonical plan file schemas with required sections and naming conventions.

91|9|Updated Dec 24, 2025

Search Tags:#automation #planning #validation #schema #conversion #plan #workflows

Ready to run

npx skills add https://github.com/GantisStorm/essentials-claude-code --skill plan-schema-gantisstorm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-schema
Source: https://github.com/GantisStorm/essentials-claude-code/tree/main/essentials/skills/plan-schema
Command: npx skills add https://github.com/GantisStorm/essentials-claude-code --skill plan-schema-gantisstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a canonical reference for plan file schemas to reduce ambiguity in plan creation.

Core Features & Use Cases

Defines the canonical .claude/plans/*-plan.md file layout, required sections, and naming conventions.
Explains how plan files feed converters to generate prd.json and beads, and how editors and runners consume them.
Use cases include creating new plan templates, validating existing plans, and mapping plan sections to downstream tooling.

Quick Start

Validate a plan file with /plan-schema against .claude/plans/my-feature-plan.md.

Frequently Asked Questions about plan-schema

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

FAQPage Schema

How do I validate a plan file schema against required sections?▼

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.

What is a plan file schema used for in automation 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.

How do I convert a validated plan file to prd.json?▼

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.

Does the plan schema work with plan editors and executors?▼

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.

What's the best way to enforce naming conventions in plan templates?▼

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.

Why does my plan file validation fail during conversion?▼

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.