SPECLAN Format

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.

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.

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.

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.

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.

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.