kdoc

Sub-agent that validates all ADRs in the Knowledge/ADR directory for numbering integrity, frontmatter completeness, cross-references, and supersession chain integrity. Called by knowledge-auditor in parallel with other sub-agents.

Orchestrator agent that runs all Knowledge governance scripts, launches specialized sub-agents in parallel, consolidates their findings, and writes a governance-health.md report. Use when the user asks for a full Knowledge audit or "knowledge-auditor".

Sub-agent that reads all roadmap phase files, cross-references TLDRs and evidence files, and generates a dashboard showing phase completion status and health. Called by knowledge-auditor in parallel with other sub-agents.

Sub-agent that validates all TLDRs in Knowledge/TLDR for gap tag consistency, status lifecycle correctness, wikilink references, and coverage against project modules. Called by knowledge-auditor in parallel with other sub-agents.

<!-- kdoc:core:start -->

Create a new Architecture Decision Record by reading the ADR template, determining the next ADR number from existing files, and writing a schema-compliant ADR. Use when the user asks to create ADRs, document architecture decisions, or record a technical decision.

Validate ADR numbering, frontmatter, supersession chains, and wikilink references by scanning ADR files directly. Use when the user asks to validate ADRs, check ADR governance, or audit the ADR directory.

Create an operational guide by reading the guide template and schema, then writing a guide under Knowledge/Guides. Use when the user asks to create a guide, create an operational guide, or write a how-to.

Create a STRIDE threat model by reading the threat-model template and schema, then writing the result under Knowledge/ThreatModels. Use when the user asks for a threat model or says threat model for a module or feature.

Create a page, screen, or flow specification by detecting the active pack, reading the relevant template, and writing a schema-aware design doc. Use when the user asks to create a page spec, create a screen spec, create a design spec, or create a flow spec.

2 hooks across 2 events