memory-schema-preflight

You validate YAML frontmatter by running local schema validators that enforce canonical rules, strict enums, and quoted string formats for version and date fields, preventing formatting errors from reaching CI.

ADR files fail CI checks when their filenames do not match required slug and regex patterns. Running a pre-commit validation step locally catches these filename pattern mismatches before they trigger continuous integration failures.

SPEC.md memory artifacts require specific Markdown section headings, including one of the allowed User Story headings. Local validators check for these required section headings to ensure document structure complies with schema constraints.

You can enforce RUNBOOK owner letter constraints locally by running validation scripts against your memory artifacts. These scripts check that owner fields comply with strict schema rules before files are written or committed.

Schema pre-validation should run before write or edit operations on files within memory directories, and before git commit when changes touch defined memory paths. This prevents repeated CI failures caused by small formatting issues.

Yes, schema validation works with session and handoff Markdown files, along with charters and requirements documents. It validates canonical YAML frontmatter and required Markdown sections across all defined memory artifact paths.