Engineering
confluence-docs avatar

confluence-docs

Standardized technical documentation templates for ADRs, runbooks, architecture, and knowledge transfer in AI agent workflows.

Introduction

The Confluence Docs skill provides a structured framework for managing technical documentation within AI-driven development environments. Designed for developers, architects, and technical writers, this skill ensures consistency across project documentation by enforcing standardized templates for Architectural Decision Records (ADRs), operational runbooks, system architecture specifications, and knowledge transfer (KT) documents. By centralizing documentation patterns, it helps teams maintain clear historical context and operational visibility, reducing cognitive load during technical reviews and system handovers.

  • Standardized ADR templates including context, decision rationale, implementation notes, and impact analysis for long-term architectural tracking.

  • Operational runbook templates covering prerequisites, step-by-step procedures, verification steps, rollback strategies, and troubleshooting workflows.

  • Architecture documentation patterns capturing high-level overviews, component dependencies, security, performance considerations, and observability metrics.

  • Knowledge transfer (KT) formats tailored for ticket-linked documentation, facilitating context sharing after complex implementation tasks.

  • Enforced documentation checklist to ensure quality, proper formatting, code block consistency, and the exclusion of sensitive security data.

  • The skill should be invoked when initiating new design decisions, documenting infrastructure services, or finalizing development features.

  • Documentation output is automatically routed to specific directories including docs/adr/, docs/runbooks/, docs/architecture/, and docs/agent-outputs/technical-docs/.

  • Files should follow defined naming conventions like ADR-XXX-{description}.md or KT-{{TICKET_PREFIX}}-XXX-{topic}.md to ensure system discoverability.

  • Adhere to the provided linting and formatting requirements, including H1-H3 hierarchy and verified Markdown lint passes to maintain project standards.

  • Ensure all architectural changes are backed by an ADR to provide an audit trail for system-wide shifts in data access patterns, CI infrastructure, or security implementations.

Repository Stats

Stars
58
Forks
14
Open Issues
8
Language
Shell
Default Branch
main
Sync Status
Idle
Last Synced
Apr 29, 2026, 02:15 PM
View on GitHub