What problem does it solve? Managed Markdown documents require a strict YAML frontmatter block with eleven required fields, controlled values, canonical key order, and a machine-validated id format. Hand-authoring this block produces quoting errors, invalid doc_type values, and low-entropy id tokens that fail CI validation. ## Core Features & Use Cases - Deterministic id generation: The bundled new-doc-id script mints {doc_type}-{base36-6}-{slug} ids using /dev/urandom entropy, avoiding collision-prone LLM-invented tokens. - Frontmatter scaffolding: --scaffold emits the full eleven-field canonical block with correctly quoted dates and empty lists, ready to fill in. - Validation guidance: Covers the rules that actually fail project-standards validate, validate-id, and format-frontmatter --check, plus a table of common mistakes and fixes. - Use Case: When creating a new runbook under docs/, run the scaffold command to get a compliant frontmatter block, then confirm the repository passes project-standards validate before committing. ## Quick Start Ask the agent to create a new runbook document named restart-netbox-after-config-change with standard-compliant frontmatter using the new-doc-id scaffold script.
