documentation-management

To organize project documentation effectively, you should apply documentation governance rules that enforce naming conventions, a standard docs/ structure, and specific templates for guides, architecture docs, ADRs, and skills.

You should archive, delete, or extract repeating documentation patterns into skills by using decision-tree prompts that help evaluate document type, usage frequency, and long-term value to determine the correct governance action.

The recommended directory structure for architecture docs and ADRs uses a standardized docs/ layout with defined locations for guides, architecture documentation, Architecture Decision Records, and skills to maintain consistency.

You create templates for guides, architecture docs, and ADRs by applying governance rules that define naming conventions and structural patterns, ensuring every new Markdown file follows consistent formatting and location standards.

Documentation governance works for auditing existing Markdown files by applying decision-tree prompts and structural policies to evaluate whether current docs should be kept, archived, deleted, or extracted into skills.

The best way to decide where new documentation belongs is to identify its type as a guide, architecture doc, ADR, or skill, then place it in the appropriate location based on governance rules and naming conventions.