plan-mode

Validate YAML frontmatter in Plan Markdown files under .kilo/plans/.

4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/cc01cc/cmtx-project --skill plan-mode-cc01cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-mode
Source: https://github.com/cc01cc/cmtx-project/tree/main/.kilo/skills-repo/shared/plan-mode
Command: npx skills add https://github.com/cc01cc/cmtx-project --skill plan-mode-cc01cc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Plan Mode enforces metadata standards for design documentation by ensuring Plan Markdown files contain proper YAML frontmatter and predictable naming.

Core Features & Use Cases

  • Enforces YAML frontmatter with required fields like title and date in ISO 8601 with timezone
  • Validates plan files using an included Python script and checks location in .kilo/plans/
  • Guides planning workflow across exploration, synthesis, and documentation phases with auto-generated file names via kilocode

Quick Start

Activate Plan Mode to guide planning by auto-generating plan files and validating their metadata.

Frequently Asked Questions about plan-mode

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

FAQPage Schema
How do I validate YAML frontmatter in Markdown plan files?

To validate YAML frontmatter in Markdown plan files, use a Python script that checks required fields like title and date in ISO 8601 format with timezone. It ensures plan files stored in .kilo/plans/ contain proper metadata for consistent design documentation.

What metadata fields are required for plan Markdown files?

Required metadata fields for plan Markdown files include title and date in ISO 8601 format with timezone. Optional fields such as description, tags, and status can be added to provide additional context for the design documentation.

How do I enforce consistent naming and metadata for design documentation?

Enforce consistent naming and metadata for design documentation by activating Plan Mode to auto-generate file names via kilocode. It validates YAML frontmatter and ensures plan files are stored under the .kilo/plans/ directory across exploration, synthesis, and documentation phases.

Do I need Python and pyyaml to use Plan Mode metadata validation?

Yes, you need Python and the pyyaml dependency to run the included validation script for Plan Mode metadata. The script uses pyyaml to parse and verify the YAML frontmatter in your plan Markdown files.

Can I validate plan files stored outside the .kilo/plans/ directory?

Plan Mode applies to plan files stored under the .kilo/plans/ directory. Files stored outside this location are not validated by the included Python script and frontmatter checks for proper metadata standards.

What is the best way to automate plan file creation with ISO 8601 dates?

The best way to automate plan file creation with ISO 8601 dates is to activate Plan Mode, which guides the planning workflow and auto-generates file names via kilocode. It automatically enforces required metadata standards during creation across all planning phases.