# Step 6 -- Confluence Documentation

## Goal

Make documentation part of the implementation workflow.

The documentation skill should work without MCP first. If approved
later, connect Claude to Atlassian/Confluence for search/create/update.

## Standard Page

-   Overview
-   Purpose
-   Architecture
-   Prerequisites
-   Licensing
-   Permissions
-   Default Configuration
-   Configurable Options
-   IaC Implementation
-   Manual Implementation
-   Validation
-   Operations
-   Rollback
-   Customer Responsibilities
-   MSSP Responsibilities
-   Exceptions
-   References
-   Last Reviewed

## Rules

Separate Microsoft guidance from organizational recommendations. Explain
why defaults exist. Mark assumptions. Identify licensing, roles, manual
steps, validation, and rollback.

## Decisions

Atlassian MCP availability, page hierarchy, review process, and whether
Git or Confluence is authoritative for each type of information.

Recommended: Git owns code/ADRs; Confluence owns consumable architecture
and operational documentation.