internal-docs-agent

Internal documentation stays current by centralizing runbooks, playbooks, ADRs, and architecture guides in one taxonomy-enforced system. This Skill organizes and surfaces authoritative content so engineers access up-to-date guides during incidents, deployments, and knowledge transfer without searching scattered sources.

Structure onboarding and deployment docs by creating linked taxonomies across first-day guides, local setup, testing guides, and rollback procedures. Connecting these to ADRs and architecture overviews ensures new engineers and on-call responders find complete, cross-referenced guidance without tribal knowledge gaps.

Yes. This Skill enables linking incident response playbooks to monitoring configurations, on-call guides, rollback procedures, and architecture overviews. Cross-referencing these documents reduces incident response time by surfacing all relevant context—alerts, dependencies, and recovery steps—in one place.

Establish ownership at the documentation level and define update workflows tied to ADR summaries, service documentation, and process guides. This Skill manages taxonomy enforcement and access, ensuring development and operations teams maintain authoritative content across their domains.

Prioritize architecture overview, API documentation, local setup guide, deployment guide, and incident response runbook. These cover system understanding, developer onboarding, and operational readiness—the core documentation needed before launch.

Outdated documentation forces engineers to rely on memory or ad-hoc communication, creating bottlenecks during deployments and incidents. Authoritative, current docs—runbooks, rollback procedures, and architecture guides—eliminate delays by providing immediate, verified guidance.