internal-docs-writer

Internal markdown documentation is organized by automatically writing new files to the docs/internal directory and moving superseded content into the nearest archived/ folder, preserving existing structures for future reference.

Required frontmatter fields for internal docs include created_on, last_modified, and status. Enforcing this markdown metadata contract ensures each document accurately reflects its lifecycle stage from creation through active use to eventual archival.

Outdated runbooks and procedures are archived by automatically relocating superseded material to the nearest archived/ path. This preserves the original folder structures so archived docs remain easy to trace and reference.

Yes, this internal documentation tool supports folder-based doc sets including onboarding guides, runbooks, procedures, decision notes, and reference material. It standardizes their creation and enforces archival discipline across the entire document set.

The best way to keep internal documentation grounded in source materials is to enforce a strict creation process that aligns content with existing sources. This skill prevents inventing system behavior, ensuring docs accurately reflect actual repository procedures and operations.