manage-markdown-docs

Standardize Markdown docs by applying enforced header metadata (document name, classification, created date, author, purpose) and an automatically maintained Change History footer. Specify the document path, and the system applies the structure and tracks modifications on every update.

Required header fields include document name, created date, classification (external-research, internal-analysis, contextual, or custom), purpose, author, and context. These fields ensure consistent traceability and improve document organization across projects.

Yes. Point the system to your existing Markdown file, and it will add required header metadata and initialize a Change History footer with the current modification. The system applies standardization to research notes, analysis reports, design documents, meeting notes, and technical documentation.

Change History is maintained as a footer table appended to each Markdown document. Every modification automatically adds a new entry, creating a timestamped audit trail without manual intervention.

Applies to any general-purpose Markdown file across workspace, monorepo, ontology, and related projects. The system determines storage location by document type or uses the provided path exactly, supporting research notes, findings, analysis reports, design documents, and technical documentation.

Yes. The system enforces Markdown lint rules and validates Mermaid diagram syntax to maintain document quality and structural consistency alongside metadata standardization.