release-format-validation

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.

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.

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.

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.

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.