document-naming-convention

To enforce consistent ADR and planning document naming, apply uppercase category prefixes and hyphen separators to filenames in adr/ and plans/ directories. This standardizes document discovery and enables automated validation across repositories.

The best way to bulk rename decision records is to audit the adr/ and plans/ directories to identify non-compliant names, then apply the built-in validator and renaming guidance to calculate and apply the correct numeric sequencing.

Automated numeric sequencing prevents file naming conflicts by assigning per-category sequential numbers to each document. It checks for existing collisions within adr/ and plans/ directories to ensure every filename is unique and ordered correctly.

Yes, you can validate document names using regex patterns across large directories. The built-in validator checks filenames against regex rules to ensure they satisfy category prefixing, numeric sequencing, and hyphen separator compliance.

Yes, this naming convention approach works for directories beyond ADR and plans. It applies to creating, renaming, and validating docs within any similar decision directories, producing metadata for discovery and audits.