header-aggregation

To standardize YAML frontmatter across Markdown files, you can batch process an entire directory to apply canonical metadata and merge it with existing values. The tool automatically derives required fields and prompts for confirmation before overwriting.

Adding canonical frontmatter to spec files enables traceability and indexing by applying standardized YAML metadata. It processes project-intent, requirement-spec, and story files to derive required fields while validating cross-references.

Merging new YAML frontmatter preserves existing Markdown metadata through a smart merge with conflict detection. The system previews the diff and prompts for user confirmation before overwriting any original frontmatter fields.

Cross-reference validation for parent and related slugs checks linked references within the YAML frontmatter to ensure they resolve correctly. Unresolved references are automatically flagged as [pending] to maintain document traceability.

You can process a single Markdown file to apply canonical YAML frontmatter instead of batch processing a full directory. The tool operates on individual files to derive required fields and validate references with user-confirmed merges.

You should avoid automated frontmatter aggregation when your Markdown docs require custom non-standard YAML fields outside the canonical spec. The tool targets specific spec file types and may flag valid custom references as unresolved [pending] items.