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.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
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.
domain
delivery
subdomain
delivery-tools
difficulty
intermediate
time-saved
TODO: Quantify time savings
frequency
TODO: Estimate usage frequency
use-cases
["Primary workflow for Confluence Expert","Analysis and recommendations for confluence expert tasks","Best practices implementation for confluence expert","Integration with related skills and workflows"]
This skill provides comprehensive Confluence expertise for creating and managing documentation spaces, knowledge bases, team collaboration areas, and strategic documentation architecture. It includes advanced macro usage, template creation, content governance frameworks, and integration patterns with Jira and other Atlassian tools through the Atlassian MCP server.
Target users include documentation specialists, knowledge managers, team leads, project managers, technical writers, and Scrum Masters who need to structure and maintain high-quality documentation in Confluence. This skill is essential for teams implementing documentation strategies, creating self-service knowledge bases, or establishing collaborative workspaces for agile teams.
Core Value: Reduce documentation creation time by 50% through templates and macros, improve content findability by 40% through proper space architecture, and increase team documentation adoption by 60% through best practices and governance frameworks.
Core Capabilities
Space Architecture & Design - Create hierarchical space structures with optimal taxonomy, navigation, permission schemes for teams, projects, and knowledge bases
Content Creation & Templates - Build reusable page templates with macros, structured layouts, and dynamic content for consistent documentation across teams
Documentation Governance - Implement content lifecycle management, review cycles, archiving strategies, and quality standards for sustainable documentation ecosystems
Atlassian MCP Integration - Direct Confluence operations via MCP server for automated page creation, space management, content synchronization, and Jira integration
Quick Start
Common Confluence Operations
This skill provides Confluence expertise through knowledge frameworks, templates, and macros. Actual Confluence operations are performed through the Atlassian MCP server configured in Claude Code settings.
Access Documentation Resources
Macro reference: See Essential Macros section for commonly used Confluence macros with examples
Template library: See Templates Library section for ready-to-use page templates (meeting notes, project overviews, decision logs, retrospectives)
Best practices: See Best Practices section for writing style, organization, maintenance, and content governance standards
Space architecture: See Page Architecture section for recommended space structures and hierarchies
Key Workflows to Start With
Create Team Documentation Space - Set up a complete team space with structure and templates (45 minutes)
Set Up Sprint Ceremony Documentation - Implement sprint planning, standup, review, and retrospective templates (1 hour)
Create Executive Reporting Page - Build live dashboard with Jira integration for stakeholder visibility (1.5 hours)
Key Workflows
1. Create Team Documentation Space
Time: 45 minutes
Steps:
Determine space type and structure - Identify if this is a Team, Project, or Knowledge Base space based on documentation goals
Team spaces: Ongoing team operations and meetings
Project spaces: Single-project centered docs
Knowledge Base: Cross-team reference materials
Create space with naming convention - Create space in Confluence using clear, consistent naming (e.g., "TEAM-Engineering" or "PROJ-ProductLaunch")
Set description, category, and initial permissions
Enable space shortcuts for key pages
Set up initial page structure - Create space homepage and primary navigation pages
Space Home (Overview & Getting Started)
├── Team Information (Members, Roles, Communication)
├── Processes & Workflows (How we work)
├── Meeting Notes (Archive of ceremonies)
└── Resources & References (External links)
Configure space permissions - Set View, Edit, Create, Delete, and Admin access for appropriate groups
Create templates for consistency - Add space templates for recurring page types (meeting notes, project overviews, retrospectives)
Expected Output: A fully operational team documentation space with clear structure, functional templates, and appropriate access controls ready for team population.
See Page Architecture section for detailed space structure patterns and best practices.
2. Set Up Sprint Ceremony Documentation
Time: 1 hour
Steps:
Create Sprint Planning template - Use template pattern from Templates Library section with agenda, attendees, and decisions
Include acceptance criteria review section
Add story point estimation placeholder
Link to sprint backlog in Jira
Create Daily Standup capture page - Simple daily page for status tracking
Format: What we completed | What's next | Blockers
Use task list macro to track impediments
Link to sprint board
Create Sprint Retrospective template - What went well, what didn't, action items
Use info/warning macros for positive/negative callouts
Link to previous retrospectives for trend analysis
Link all templates to Jira sprint - Connect Confluence pages to Jira sprint epic using Jira embed macros
Expected Output: Complete sprint ceremony documentation system with linked templates, ready for team to use in upcoming sprint cycle. Ceremonies will have consistent structure and documented artifacts.
Embed Jira reports - Use Jira Chart and Filter Results macros
Sprint velocity chart
Issue breakdown by status
Overdue items query
Document key risks and decisions - Create risk register and decision log sections
Link to detailed risk register page
Recent important decisions with rationale
Set up automated content updates - Configure "Recently Updated" and "Content by Label" macros to pull relevant data
Expected Output: Live executive dashboard page in Confluence that provides stakeholder visibility into project health, metrics, and decisions. Dashboard updates automatically as team creates content and updates Jira.
4. Implement Documentation Governance Process
Time: 2 hours (setup) + ongoing maintenance
Steps:
Define documentation standards - Create style guide and quality checklist
Writing style: active voice, scannable content
Naming conventions for pages and spaces
Metadata requirements (owner, last updated, review date)
See Content Quality Checklist in Best Practices section
Create content review schedule - Establish review cycles by content type
Critical docs: Monthly review
Standard docs: Quarterly review
Archive docs: Annual retention review
Set up labeling system - Create labels for organization and filtering
Status labels: outdated, reviewed, needs-update
Team labels: backend, frontend, product
Type labels: how-to, reference, decision, meeting-notes
Create archiving workflow - Move outdated content to Archive space with date labels
Expected Output: Established documentation governance system with clear standards, review schedule, and archiving process. Team has framework for maintaining documentation quality over time.
See Content Governance section for archiving strategy and quality checklist.
Python Tools
This skill does not include Python automation tools. Confluence operations are performed directly through the Atlassian MCP server, which provides native integration for:
Creating and managing spaces
Creating, updating, and deleting pages
Applying templates and macros
Managing page hierarchies
Configuring permissions
Searching content
Extracting documentation for analysis
See the Atlassian MCP Integration section below for detailed integration patterns and capabilities.
Reference Documentation
The following sections provide comprehensive frameworks, templates, and best practices for Confluence expertise:
Core Competencies
Space Architecture
Design and create space hierarchies
Organize knowledge by teams, projects, or topics
Implement documentation taxonomies
Configure space permissions and visibility
Content Creation
Create structured pages with layouts
Use macros for dynamic content
Build templates for consistency
Implement version control and change tracking
Collaboration & Governance
Facilitate team documentation practices
Implement review and approval workflows
Manage content lifecycle
Establish documentation standards
Integration & Automation
Link Confluence with Jira
Embed dynamic Jira reports
Configure page watchers and notifications
Set up content automation
Workflows
Space Creation
Determine space type (Team, Project, Knowledge Base, Personal)
Create space with clear name and description
Set space homepage with overview
Configure space permissions:
View, Edit, Create, Delete
Admin privileges
Create initial page tree structure
Add space shortcuts for navigation
HANDOFF TO: Teams for content population
Page Architecture
Best Practices:
Use page hierarchy (parent-child relationships)
Maximum 3 levels deep for navigation
Consistent naming conventions
Date-stamp meeting notes
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
Template Creation
Identify repeatable content pattern
Create page with structure and placeholders
Add instructions in placeholders
Format with appropriate macros
Save as template
Share with space or make global
USE: References for advanced template patterns
Documentation Strategy
Assess current documentation state
Define documentation goals and audience
Organize content taxonomy and structure
Create templates and guidelines
Migrate existing documentation
Train teams on best practices
Monitor usage and adoption
REPORT TO: Senior PM on documentation health
Knowledge Base Management
Article Types:
How-to guides
Troubleshooting docs
FAQs
Reference documentation
Process documentation
Quality Standards:
Clear title and description
Structured with headings
Updated date visible
Owner identified
Reviewed quarterly
Essential Macros
Content Macros
Info, Note, Warning, Tip:
{info}
Important information here
{info}
Expand:
{expand:title=Click to expand}
Hidden content here
{expand}
