Prompt Library

ChatGPT Prompts for Confluence (Wiki + Docs)

20 copy-paste prompts

20 copy-paste ChatGPT prompts for Confluence: space architecture, page templates, knowledge base, search optimization, and the workflows that prevent Confluence from becoming abandoned doc graveyard.

Space Architecture

4 prompts

Space Hierarchy Design

1/20

Design Confluence space hierarchy for [team / org]. Output: spaces (one-per-team), page tree depth (3 levels max), navigation strategy, ownership per space. Space sprawl = unfindable.

Designs Confluence spaces.

💡

Pro tip: Default Confluence = space sprawl in 6 months. Disciplined (one space per team, max 3-level depth) = sustainable.

Page Tree Strategy

2/20

Page tree for [space]. Output: top-level page categories, sub-page logic, what goes where, what does NOT belong here. Page tree = navigation.

Plans page trees.

💡

Pro tip: Random nesting = unfindable. Designed page tree (matching real workflow) = navigable. Investment in tree structure = readers find.

Wiki vs Doc-Per-Project

3/20

Wiki structure vs doc-per-project decision. Output: wiki for: living docs, processes, knowledge. Doc-per-project for: project-specific, time-bound. Mix patterns.

Decides wiki vs project docs.

💡

Pro tip: Wiki content = living, evergreen, searchable. Project docs = time-bound. Mixing = confusing both. Distinct purposes.

Confluence + Jira Integration

4/20

Integration strategy: Confluence + Jira. Output: when to link Confluence page from Jira ticket, project pages structure, decision logs, requirements docs. Tools complement.

Integrates Confluence + Jira.

💡

Pro tip: Jira = task-level. Confluence = context-level. Linking = unified context. Most teams use one + miss the other.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

Page Templates

4 prompts

Meeting Notes Template

5/20

Confluence meeting notes template. Output: header (date, attendees, agenda link), discussion section, decisions, action items, parking lot, next meeting. Built-in template + customization.

Templates meeting notes.

💡

Pro tip: Confluence built-in templates good starting point. Customize for team specifics. Templated notes = institutional consistency + searchability.

Decision Doc Template

6/20

Decision doc template. Output: decision being made, context, options + pros/cons, recommendation, decision (filled when made), rationale, dissenting views, sign-off. Documented decisions stick.

Templates decision docs.

💡

Pro tip: Decisions in chat = re-litigated. Decisions in Confluence = closed + searchable. "What did we decide about X 6 months ago?" = answerable.

Project Brief Template

7/20

Project brief Confluence template. Output: project name, owner, status (live), problem, goals/non-goals, approach, timeline, risks, FAQ (live doc). Living brief.

Templates project briefs.

💡

Pro tip: Project briefs frozen at kickoff = stale. Living Confluence page updated through project = current truth. Most teams write at kickoff + abandon.

Architecture Decision Record (ADR)

8/20

ADR template for engineering. Output: title, status (proposed/accepted/superseded), context, decision, consequences, alternatives considered. Architecture context = engineering knowledge.

Templates ADRs.

💡

Pro tip: Engineering decisions undocumented = re-discussed every 18 months. ADRs = "we decided X for reasons Y; consequences Z." Engineering institutional memory.

Knowledge Management

4 prompts

Knowledge Base Structure

9/20

Knowledge base structure for [topic — onboarding, customer support, engineering practices]. Output: top-level categories, sub-categories, search optimization, FAQ sections, ownership. KB done well = institutional asset.

Builds knowledge bases.

💡

Pro tip: KB without structure = pile. KB with structure + maintenance = institutional asset. Most KBs decay; the discipline of maintenance matters.

Page Quality Audit

10/20

[Paste page]. Audit: clear purpose, scannable structure (H2s + bullets), accurate (verify), complete (no gaps), current (or marked stale). Most pages decay over time.

Audits page quality.

💡

Pro tip: Pages written + abandoned = decay. Quality audit + ownership + review cadence = sustainable. Without audit = KB becomes museum.

Search Optimization

11/20

Optimize page for Confluence search. Output: title with keywords, page summary at top, headings hierarchy, tags/labels, related pages linked. Confluence search = how readers find.

Optimizes for search.

💡

Pro tip: Pages unfindable = unread. Title + summary + tags = findable. Most pages skip optimization; the discipline = readership.

Outdated Page Strategy

12/20

Strategy for outdated/stale pages. Output: detection (last edited > 6 months), notification to owner, archive vs update vs delete, audit cadence. Stale pages = bad signals.

Manages stale pages.

💡

Pro tip: Stale pages = readers find wrong info. Quarterly audit + archive/update = clean. Without governance = KB rotted in 2 years.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Workflows + Power Use

4 prompts

Approval Workflow

13/20

Approval workflow for Confluence pages. Output: trigger (publication, change), approver chain, approval form, archive policy on rejection. Built into Confluence Premium; alternative for free tier.

Builds approval workflows.

💡

Pro tip: Confluence Premium = built-in approvals. Free tier = manual via macros + status labels. Critical for: policies, compliance docs, customer-facing pages.

Macro Strategy

14/20

Macros to use in Confluence pages. Output: TOC (auto-generated), Status, Info/Warning panels, Roadmap, Excerpt include, Page tree. When each appropriate. Macros = enhanced pages.

Plans macro usage.

💡

Pro tip: Plain pages vs macro-enhanced = different reading experience. TOC at top of long pages = navigable. Status labels = visible. Most users skip macros.

Sharing + Permissions

15/20

Sharing strategy for [content]. Output: space-level permissions (view/edit), page-level overrides if sensitive, external access, audit cadence. Default permissive = security risk.

Plans Confluence permissions.

💡

Pro tip: Default Confluence = space-wide visibility. Sensitive content (executive, HR, legal) = page-level restrictions. Audit annually for drift.

Onboarding to Confluence

16/20

New team member onboarding to Confluence. Output: which spaces to know, key pages to bookmark, search tips, contribution norms (when to create page vs add to existing). Most onboarding skips wiki.

Onboards new members.

💡

Pro tip: New member dropped into Confluence = lost. Onboarding tour + key pages + search tips = productive in week 1, not month 3.

AI in Confluence

4 prompts

Atlassian Intelligence Use

17/20

Use Atlassian Intelligence in Confluence. Capabilities: summarize page, write/improve content, find content, generate from prompt. Output: when each appropriate, prompt patterns. Native AI > pasting to ChatGPT.

Uses Atlassian Intelligence.

💡

Pro tip: Atlassian Intelligence = native AI in Confluence. Prompts in-context. Better than ChatGPT for Confluence-specific work; trained on Atlassian content.

Page Summarization Strategy

18/20

Summarize long pages strategically. Output: when to summarize (top of long page), how (manual vs AI), what summary should include, length. Summary = scan-ability.

Plans page summarization.

💡

Pro tip: 5-page Confluence pages = first paragraph carries the load. Strong summary at top + detail below = readers get both. Most pages just dive in.

Content Generation from Notes

19/20

[Paste rough notes]. Generate Confluence page from notes. Output: structured page with headings, summary at top, action items, related links. Notes → polished doc.

Generates pages from notes.

💡

Pro tip: Rough notes accumulating = dropped. AI-generated polished page from notes = institutional knowledge. Discipline of upgrading notes pays.

AI Search Patterns

20/20

Use Atlassian Intelligence search effectively. Output: question-style queries (vs keyword), follow-up questions, when to fall back to traditional search. AI search = different patterns.

Uses AI-powered search.

💡

Pro tip: Traditional search = keywords. AI search = questions ("how do we handle customer escalations?"). Different patterns; different results. Most users still keyword-search.

Frequently Asked Questions

Confluence: deep wiki features, Atlassian ecosystem, enterprise. Notion: modern UI, blocks, more flexible. Google Docs: real-time collab, simpler. Engineering teams often Confluence; modern startups often Notion.

Yes by default. Without active management = stale in 12 months. Active management (ownership, audit cadence, archive policy) = sustainable. The discipline matters more than the tool.

Page ownership + last-reviewed metadata. Most pages have no owner; nobody maintains. Owner + quarterly review = sustainable. Without = decay.

Page titles often optimized for author, not searcher. Use page tags/labels. Atlassian Intelligence (Premium) = AI-powered search better than keyword. Most "missing" content = bad titling, not bad indexing.

Free tier = up to 10 users. Standard ($5/user/mo) = useful features. Premium ($10) = AI + advanced. Worth it for engineering + product teams using daily; less for occasional users.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial Explore AI for Product Managers

7-day free trial. Cancel anytime.

Browse All Prompt Collections