plan-schema

Validate markdown plan files against a canonical schema.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/Dethon/ai-dev-flow --skill plan-schema
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-schema
Source: https://github.com/Dethon/ai-dev-flow/tree/main/skills/plan-schema
Command: npx skills add https://github.com/Dethon/ai-dev-flow --skill plan-schema

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a canonical reference and validation framework for plan files used by plan creators to ensure consistent structure and predictable execution.

Core Features & Use Cases

  • Guided plan structure: Enforces required sections and section order for docs/plans/*-plan.md.
  • Validation tooling: Supports validation of plan files to ensure completeness and correctness.
  • Use Case: When designing a new feature plan, use this Skill to ensure the plan adheres to the canonical schema before execution.

Quick Start

Invoke /plan-schema validate docs/plans/{feature-slug}-{hash5}-plan.md to validate a plan file.

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 markdown plan file for consistent structure?

To validate a markdown plan file, invoke the plan-schema validation command against your docs/plans/*-plan.md file to enforce required sections, section order, and a strict dependency graph for consistency.

What sections are required in a canonical architectural plan document?

A canonical architectural plan document requires specific enforced sections, a strict section order, per-file entries with detailed sub-sections, and a strict dependency graph to ensure predictable execution and reproducibility.

How do I enforce a strict dependency graph in my feature planning workflow?

You can enforce a strict dependency graph by applying a canonical plan schema to your markdown plans, which validates the structural dependencies and per-file entries during the plan creation and review process.

Can I use this plan schema validation for markdown files outside the docs/plans directory?

This plan schema validation is specifically designed for markdown-based plans stored under the docs/plans/*-plan.md path, ensuring consistency across the architectural planning workflow rather than generic markdown files.

Why does my architectural plan fail the validation review process?

An architectural plan fails validation when it lacks required sections, violates the enforced section order, omits detailed per-file sub-sections, or contains an incomplete strict dependency graph according to the canonical schema.

Do I need any external dependencies to create and validate plan files?

No external dependencies are required to create and validate plan files; the schema operates directly on markdown-based plans to enforce structural consistency and completeness without additional tools.