// Atlassian Confluence expert for creating and managing spaces, knowledge bases, documentation, planning, product discovery, page layouts, macros, templates, and all Confluence features. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management.
Expert agile coaching for team transformation, framework selection, maturity assessment, and organizational change management. Use when selecting an agile framework for a team, coaching through Tuckman development stages, facilitating retrospectives, assessing organizational agile maturity, or designing a transformation roadmap.
Atlassian Administrator for managing and organizing Atlassian products, users, customization of the Atlassian suite, permissions, security, integrations, system configuration, and all administrative features. Use for user provisioning, global settings, security policies, system optimization, and org-wide Atlassian governance.
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use for building org-wide templates, custom blueprints, page layouts, and automated content generation.
Structured PM 1:1 templates by partner type — with manager, engineering manager partner, designer, IC reports — grounded in Radical Candor, the GROW coaching model, and the Manager Tools 1:1 framework.
PM career ladder rubrics from APM through VP/CPO across product sense, execution, leadership, strategy, and communication. Includes gap analysis, growth planning, and promotion packet templates.
Structured PM interview preparation across product sense, execution, strategy, behavioral, and technical rounds, using CIRCLES, AARM, STAR, and the estimation framework. Calibrated to APM, PM, Senior PM, and Group PM rubrics.
| name | confluence-expert |
| description | Atlassian Confluence expert for creating and managing spaces, knowledge bases, documentation, planning, product discovery, page layouts, macros, templates, and all Confluence features. Use for documentation strategy, space architecture, content organization, and collaborative knowledge management. |
| license | MIT + Commons Clause |
| metadata | {"version":"1.0.0","author":"borghei","category":"project-management","domain":"atlassian","updated":"2026-03-31T00:00:00.000Z","tags":["confluence","knowledge-management","wiki","documentation"]} |
Master-level expertise in Confluence space management, documentation architecture, content creation, macros, templates, and collaborative knowledge management.
Space Architecture
Content Creation
Collaboration & Governance
Integration & Automation
Best Practices:
Recommended Structure:
Space Home
├── Overview & Getting Started
├── Team Information
│ ├── Team Members & Roles
│ ├── Communication Channels
│ └── Working Agreements
├── Projects
│ ├── Project A
│ │ ├── Overview
│ │ ├── Requirements
│ │ └── Meeting Notes
│ └── Project B
├── Processes & Workflows
├── Meeting Notes (Archive)
└── Resources & References
Article Types:
Quality Standards:
Info, Note, Warning, Tip:
{info}
Important information here
{info}
Expand:
{expand:title=Click to expand}
Hidden content here
{expand}
Table of Contents:
{toc:maxLevel=3}
Excerpt & Excerpt Include:
{excerpt}
Reusable content
{excerpt}
{excerpt-include:Page Name}
Jira Issues:
{jira:JQL=project = PROJ AND status = "In Progress"}
Jira Chart:
{jirachart:type=pie|jql=project = PROJ|statType=statuses}
Recently Updated:
{recently-updated:spaces=@all|max=10}
Content by Label:
{contentbylabel:label=meeting-notes|maxResults=20}
Status:
{status:colour=Green|title=Approved}
Task List:
{tasks}
- [ ] Task 1
- [x] Task 2 completed
{tasks}
User Mention:
@username
Date:
{date:format=dd MMM yyyy}
Two-Column Layout:
{section}
{column:width=50%}
Left content
{column}
{column:width=50%}
Right content
{column}
{section}
Panel:
{panel:title=Panel Title|borderColor=#ccc}
Panel content
{panel}
Code Block:
{code:javascript}
const example = "code here";
{code}
**Date**: {date}
**Attendees**: @user1, @user2
**Facilitator**: @facilitator
## Agenda
1. Topic 1
2. Topic 2
## Discussion
- Key point 1
- Key point 2
## Decisions
{info}Decision 1{info}
## Action Items
{tasks}
- [ ] Action item 1 (@owner, due date)
- [ ] Action item 2 (@owner, due date)
{tasks}
## Next Steps
- Next meeting date
{panel:title=Project Quick Facts}
**Status**: {status:colour=Green|title=Active}
**Owner**: @owner
**Start Date**: DD/MM/YYYY
**End Date**: DD/MM/YYYY
**Budget**: $XXX,XXX
{panel}
## Executive Summary
Brief project description
## Objectives
1. Objective 1
2. Objective 2
## Key Stakeholders
| Name | Role | Responsibility |
|------|------|----------------|
| @user | PM | Overall delivery |
## Milestones
{jira:project=PROJ AND type=Epic}
## Risks & Issues
| Risk | Impact | Mitigation |
|------|--------|-----------|
| Risk 1 | High | Action plan |
## Resources
- [Design Docs](#)
- [Technical Specs](#)
**Decision ID**: PROJ-DEC-001
**Date**: {date}
**Status**: {status:colour=Green|title=Approved}
**Decision Maker**: @decisionmaker
## Context
Background and problem statement
## Options Considered
1. Option A
- Pros:
- Cons:
2. Option B
- Pros:
- Cons:
## Decision
Chosen option and rationale
## Consequences
Expected outcomes and impacts
## Next Steps
- [ ] Action 1
- [ ] Action 2
**Sprint**: Sprint XX
**Date**: {date}
**Team**: Team Name
## What Went Well
{info}
- Positive item 1
- Positive item 2
{info}
## What Didn't Go Well
{warning}
- Challenge 1
- Challenge 2
{warning}
## Action Items
{tasks}
- [ ] Improvement 1 (@owner)
- [ ] Improvement 2 (@owner)
{tasks}
## Metrics
**Velocity**: XX points
**Completed Stories**: X/X
**Bugs Found**: X
Public Space:
Team Space:
Project Space:
Review Cycles:
Archiving Strategy:
Content Quality Checklist:
When to Escalate to Atlassian Admin:
When to Collaborate with Jira Expert:
When to Support Scrum Master:
When to Support Senior PM:
FROM Senior PM:
TO Senior PM:
FROM Scrum Master:
TO Scrum Master:
WITH Jira Expert:
Writing Style:
Organization:
Maintenance:
Usage Metrics:
Health Indicators:
Primary Tool: Confluence MCP Server
Key Operations:
Integration Points:
| Problem | Likely Cause | Resolution |
|---|---|---|
| Users cannot find existing documentation | Poor space/page hierarchy, missing labels, or unclear page titles | Restructure to max 3 levels deep; enforce descriptive naming conventions; add labels to all pages and use contentbylabel macro for discovery |
| Confluence search returns irrelevant results | Page titles are generic, content lacks keywords, or spaces have too many orphaned pages | Use specific, descriptive titles; add excerpt macros for search snippets; audit and remove orphaned pages quarterly |
| Pages become stale with outdated information | No content ownership model, no review cadence, or no visible "last updated" date | Assign a page owner to every active page; set quarterly review reminders; add {date} macro to show last update prominently |
| Space permissions are too permissive or too restrictive | Ad-hoc permission changes without a governance model; individual permissions used instead of groups | Reset to group-based permissions; define 3-4 standard permission schemes; audit permissions quarterly |
| Jira macros embedded in pages show errors or no data | JQL references deleted projects, or the viewer lacks Jira permissions for the referenced project | Verify JQL validity; ensure Confluence viewers also have Jira browse permissions for referenced projects |
| Content duplication across multiple spaces | No single source of truth policy; teams copy content instead of linking | Implement excerpt-include pattern for shared content; establish content ownership map; use cross-space linking instead of copying |
| Page tree becomes too deep (>5 levels) creating navigation fatigue | Organic growth without architectural review; no archiving strategy | Flatten hierarchy to max 3 levels; archive completed project pages; use labels and search instead of deep nesting |
In Scope: Space creation and architecture, page hierarchy design, template creation and management, content governance (review cycles, archiving, quality standards), macro usage and dynamic content, documentation strategy, knowledge base management, Jira-Confluence integration, content analytics.
Out of Scope: Global Atlassian administration (hand off to atlassian-admin/), Jira project configuration (hand off to jira-expert/), template design and governance (hand off to atlassian-templates/), sprint execution artifacts (hand off to scrum-master/).
Limitations: Confluence Cloud has storage limits per plan tier that affect attachment-heavy spaces. Advanced analytics (page view trends, contributor activity) require Confluence Premium or marketplace apps. Space-level permissions cannot override more restrictive org-wide security policies set by atlassian-admin/. Content migration between spaces can break internal links and require manual fixup.
| Integration | Direction | What Flows |
|---|---|---|
jira-expert/ | Bidirectional | Jira macros in Confluence pages; Confluence page links in Jira issue descriptions |
atlassian-admin/ | Admin -> Confluence | Global templates, space permission schemes, blueprint configuration |
atlassian-templates/ | Templates -> Confluence | Designed templates deployed to spaces; template usage guidelines |
scrum-master/ | SM -> Confluence | Sprint ceremony documentation needs, team working agreement pages |
senior-pm/ | PM -> Confluence | Executive report pages, portfolio documentation, stakeholder communication |
delivery-manager/ | DM -> Confluence | Post-mortem documentation, runbooks, release notes pages |