release-format-validation

Validate release specification files against the required template structure.

1|Updated Apr 8, 2026

Search Tags:#template #markdown #release #spec #validate #frontmatter

Ready to run

npx skills add https://github.com/dariopalminio/agile-sddf --skill release-format-validation

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill ensures a release specification file conforms to the standard release-spec-template.md, enabling consistent governance and gating quality before planning or deployment.

Core Features & Use Cases

Frontmatter validation: checks for mandatory fields Title, Version, Status, and Date.
Section validation: dynamically derives required sections from the template (Descripción, Features, Flujos Críticos / Smoke Tests) and verifies their presence.
Error reporting: returns APROBADO when compliant or REFINAR with a list of missing items to fix.

Quick Start

Provide the path to a release-spec file to validate its structure against the template.

Frequently Asked Questions about release-format-validation

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

FAQPage Schema

How do I validate a markdown release spec against a template?▼

To validate a markdown release spec, provide the file path to check its structure against the release-spec-template. The validator enforces mandatory frontmatter fields and required sections, returning APROBADO if compliant or REFINAR with missing items.

What frontmatter fields are required in a release specification file?▼

The required frontmatter fields in a release specification file are Title, Version, Status, and Date. The validation process checks for these specific fields to ensure the markdown file adheres to the standard template before deployment planning.

How do I check if my release spec includes the mandatory sections?▼

To check for mandatory sections, the validator dynamically derives requirements from the template and verifies the presence of Descripción, Features, and Flujos Críticos / Smoke Tests. It returns a REFINAR status listing any missing sections.

Can I validate a release spec using just the release name instead of a file path?▼

Yes, you can validate using a release name instead of a file path. The validator resolves the release name to a single file within the docs/specs/releases directory when possible, checking its frontmatter and section structure against the template.

What does it mean when my release spec validation returns REFINAR?▼

When validation returns REFINAR, it means the release spec is not yet compliant with the template. The result includes a detailed list of missing frontmatter fields or required sections that you must fix before the specification can be approved.