Docs Templates

To prevent stale documentation in agent workflows, apply just-in-time templates and source-verification headers that cross-check referenced paths, exports, and configs. This enforces strict freshness rules and stops hallucinated docs during on-demand generation.

Source verification for architecture documentation is a compliance protocol requiring a standardized header and checklist. It cross-checks referenced source paths, exports, and environment usage to eliminate hallucinated information in generated docs.

Generate CLI and deployment docs on demand by triggering the `/docs new` workflow with selected reference templates. The process enforces source-verification guardrails and freshness rules to ensure output accuracy and prevent hallucinated information.

Yes, graph metadata supports traceability for generated documentation. When `.beads/graph/` exists, the documentation workflow optionally integrates graph-aware behavior to anchor tracing and detect stale docs.

Template-based agent-generated docs require strict YAML-defined skill discovery and compliance with verification headers. Without optional graph metadata in `.beads/graph/`, advanced traceability and automated stale-doc detection features remain unavailable.