SPECLAN Format

Standardize SPECLAN specification files with YAML frontmatter and directory conventions.

8|Updated Jan 11, 2026

Search Tags:#workflow #requirements #validation #specifications #features #yaml-frontmatter #speclan

Ready to run

npx skills add https://github.com/thlandgraf/cc-marketplace --skill speclan-format

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: SPECLAN Format
Source: https://github.com/thlandgraf/cc-marketplace/tree/main/plugins/speclan/skills/speclan-format
Command: npx skills add https://github.com/thlandgraf/cc-marketplace --skill speclan-format

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

SPECLAN Format standardizes how specifications are authored and organized, reducing ambiguity and enabling reliable tooling by enforcing consistent frontmatter, IDs, and lifecycle rules.

Core Features & Use Cases

Establishes YAML frontmatter conventions for all SPECLAN entities (goal, feature, requirement, template, changeRequest) and defines required fields and relationships.
Enforces directory and file naming patterns, supports template usage, and enables bidirectional linking across the SPECLAN hierarchy.
Supports reading, writing, and validating SPECLAN specs, including lifecycle transitions and referencing across entities.

Quick Start

Create or update specs by adding YAML frontmatter to Markdown files and organizing them under the speclan/ directory following the goals/features/requirements structure.

Frequently Asked Questions about SPECLAN Format

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

FAQPage Schema

How do I standardize specification files using YAML frontmatter and directory conventions?▼

Standardize specification files by adding YAML frontmatter to Markdown files and organizing them under a structured directory following goals, features, and requirements patterns. This enforces consistent filenames, frontmatter validation, and lifecycle rules across all specification entities to reduce ambiguity.

What are the required frontmatter fields for validating specification entities like goals and requirements?▼

Validating specification entities requires YAML frontmatter with defined identifiers, status fields, and linked references. These rules apply to goals, features, requirements, templates, and change requests, ensuring bidirectional linking and reliable lifecycle transitions across the specification hierarchy.

How do I manage lifecycle status transitions and bidirectional linking in requirement specifications?▼

Manage lifecycle status transitions by applying enforced rules within the YAML frontmatter of your specification files. This supports bidirectional linking across the hierarchy, enabling reliable creation, validation, and editing of goals, features, and requirements.

When do I need a standardized format for requirements and feature specifications?▼

A standardized specification format is needed when reducing ambiguity and enabling reliable tooling across complex project hierarchies. It establishes consistent identifiers, directory structures, and lifecycle rules for reading, writing, and validating feature and requirement entities.

Can I use Markdown templates to create and validate change requests in a specification hierarchy?▼

Yes, you can use Markdown templates to create and validate change requests within the specification directory. The format supports template usage and enforces naming patterns, ensuring change requests maintain consistent frontmatter and proper bidirectional references.

What is the best way to structure a specification directory to avoid ambiguity in feature requirements?▼

Structure your specification directory by organizing Markdown files into goals, features, and requirements subdirectories with enforced naming conventions. This standardizes frontmatter validation and lifecycle rules, preventing ambiguity and ensuring consistent linked references across all entities.