header-aggregation

Standardize YAML frontmatter across Markdown spec files with batch processing.

1|Updated Apr 8, 2026

Search Tags:#markdown #yaml #metadata #traceability #docs #frontmatter

Ready to run

npx skills add https://github.com/dariopalminio/agile-sddf --skill header-aggregation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: header-aggregation
Source: https://github.com/dariopalminio/agile-sddf/tree/main/.claude/skills/header-aggregation
Command: npx skills add https://github.com/dariopalminio/agile-sddf --skill header-aggregation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically standardize YAML frontmatter across Markdown spec files (project-intent, requirement-spec, project-plan, release-, story-) to enable traceability, indexing, and Wiki-like navigation. Supports single-file updates or batch processing with safe, user-confirmed merges.

Core Features & Use Cases

Automatic frontmatter standardization across docs and templates for consistent metadata.
Batch processing mode to apply changes to an entire directory without manual edits.
Smart merge with conflict detection, diff preview, and user confirmation before overwriting.
Cross-reference validation for related and parent slugs, marking unresolved references as [pending].

Quick Start

Process a single Markdown file or an entire directory to apply the canonical YAML frontmatter and review proposed changes before applying.

Frequently Asked Questions about header-aggregation

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

FAQPage Schema

How do I standardize YAML frontmatter across multiple Markdown files?▼

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.

What is the best way to add canonical frontmatter to project spec files?▼

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.

How do I merge new YAML frontmatter without losing existing Markdown metadata?▼

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.

How does cross-reference validation work for parent and related slugs in frontmatter?▼

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.

Can I process a single Markdown file instead of batch processing a whole directory?▼

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.

When should I not use automated frontmatter aggregation for my docs?▼

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.