Skill: Confluence Product Documentation

Purpose

Create and maintain product documentation including Business Requirements Documents (BRDs), Product Requirements Documents (PRDs), and feature specifications.

When to Use

• Business Analyst creates BRD for new feature
• Product Owner documents product vision
• Business Analyst documents feature specifications
• Product Owner updates roadmap documentation

MCP Tools Used

Tool	Purpose
Atlassian:createConfluencePage	Create new documentation
Atlassian:updateConfluencePage	Update existing docs
Atlassian:getConfluencePage	Read current content
Atlassian:searchConfluenceUsingCql	Find existing docs
Atlassian:getPagesInConfluenceSpace	List pages in space

Configuration

{
  "cloudId": "{{confluence.cloudId}}",
  "spaceId": "{{confluence.spaceId}}",
  "spaceKey": "{{confluence.spaceKey}}",
  "parentPages": {
    "product": "{{confluence.parentPages.product}}"
  }
}

---

Business Requirements Document (BRD)

BRD Template

# BRD: {{featureName}}

**Document ID:** BRD-{{number}}
**Author:** Business Analyst Agent
**Created:** {{date}}
**Status:** Draft | In Review | Approved
**Related Epic:** {{jiraEpic}}

---

## Executive Summary

[2-3 sentence overview of the feature and its business value]

---

## Business Objectives

### Problem Statement
[What problem does this solve?]

### Business Goals
- [Goal 1]
- [Goal 2]

### Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| [Metric] | [Target] | [How measured] |

---

## Stakeholders

| Role | Name | Interest |
|------|------|----------|
| Sponsor | | |
| Primary User | | |
| Secondary User | | |

---

## Requirements

### Functional Requirements

#### FR-1: [Requirement Name]
**Priority:** Must Have | Should Have | Could Have
**Description:** [Detailed description]
**Acceptance Criteria:**
- [ ] [Criterion 1]
- [ ] [Criterion 2]

#### FR-2: [Requirement Name]
...

### Non-Functional Requirements

| Category | Requirement |
|----------|-------------|
| Performance | |
| Security | |
| Accessibility | |
| Scalability | |

---

## User Stories

| Story ID | Summary | Priority | Points |
|----------|---------|----------|--------|
| [PROJ-XX] | [Summary] | Must Have | 5 |

---

## Assumptions & Constraints

### Assumptions
- [Assumption 1]

### Constraints
- [Constraint 1]

### Dependencies
- [Dependency 1]

---

## Out of Scope

- [Item explicitly excluded]

---

## Appendix

### Glossary
| Term | Definition |
|------|------------|

### References
- [Reference 1]

Create BRD Example

Atlassian:createConfluencePage({
  cloudId: "{{confluence.cloudId}}",
  spaceId: "{{confluence.spaceId}}",
  parentId: "{{confluence.parentPages.product}}",
  title: "BRD: User Authentication System",
  body: `# BRD: User Authentication System

**Document ID:** BRD-001
**Author:** Business Analyst Agent
**Created:** 2025-01-06
**Status:** Draft
**Related Epic:** MDDEV-100

---

## Executive Summary

Implement a secure user authentication system enabling users to register, log in, and manage their accounts. This is foundational for personalized user experiences.

---

## Business Objectives

### Problem Statement
Users currently cannot create accounts or access personalized features.

### Business Goals
- Enable user registration and authentication
- Support personalized user experiences
- Establish security foundation

### Success Metrics
| Metric | Target | Measurement |
|--------|--------|-------------|
| Registration completion | >80% | Analytics |
| Login success rate | >95% | Monitoring |
| Auth response time | <200ms | APM |

---

## Requirements

### Functional Requirements

#### FR-1: User Registration
**Priority:** Must Have
**Description:** Users can create accounts with email and password
**Acceptance Criteria:**
- [ ] Email validation required
- [ ] Password strength requirements enforced
- [ ] Email verification sent

#### FR-2: User Login
**Priority:** Must Have
**Description:** Users can log in with credentials
**Acceptance Criteria:**
- [ ] Email/password authentication
- [ ] Session management
- [ ] Remember me option

---

## User Stories

| Story ID | Summary | Priority | Points |
|----------|---------|----------|--------|
| MDDEV-101 | User can register | Must Have | 5 |
| MDDEV-102 | User can log in | Must Have | 3 |
| MDDEV-103 | User can reset password | Must Have | 5 |
`,
  contentFormat: "markdown"
})

---

Feature Specification

Feature Spec Template

# Feature: {{featureName}}

**Version:** 1.0
**Last Updated:** {{date}}
**Owner:** Product Owner

---

## Overview

[Brief description of the feature]

## User Value

**As a** [user type]
**I want to** [capability]
**So that** [benefit]

## Feature Details

### Capabilities
- [Capability 1]
- [Capability 2]

### User Flow
1. [Step 1]
2. [Step 2]
3. [Step 3]

### Business Rules
- [Rule 1]
- [Rule 2]

## Edge Cases

| Scenario | Expected Behavior |
|----------|-------------------|
| [Scenario] | [Behavior] |

## Related Documentation
- BRD: [Link]
- Technical Spec: [Link]
- Design Spec: [Link]

---

Product Vision Document

Create Product Vision

Atlassian:createConfluencePage({
  cloudId: "{{confluence.cloudId}}",
  spaceId: "{{confluence.spaceId}}",
  parentId: "{{confluence.parentPages.product}}",
  title: "Product Vision - {{project.name}}",
  body: `# Product Vision

## Vision Statement

[One sentence vision]

## Target Users

| Persona | Description | Primary Need |
|---------|-------------|--------------|
| [Persona] | [Description] | [Need] |

## Key Differentiators

- [Differentiator 1]
- [Differentiator 2]

## Success Criteria

- [Criterion 1]
- [Criterion 2]

## Roadmap Overview

### Phase 1: MVP
- [Feature 1]
- [Feature 2]

### Phase 2: Enhancement
- [Feature 3]
- [Feature 4]
`,
  contentFormat: "markdown"
})

---

Used By Agents

Agent	Document Types
Business Analyst	BRDs, Feature Specs
Product Owner	Vision, Roadmap, Feature Specs
Orchestrator	References for context

Error Handling

Error	Cause	Resolution
400 Bad Request	Invalid markdown	Check formatting
404 Not Found	Parent page missing	Create parent first
409 Conflict	Title exists	Update existing or rename