Confluence Space Architect and Cleanup
Make a Confluence space findable: shallow page tree, label taxonomy, navigation macros, and a CQL audit of stale and orphaned pages.
Before & after
Same prompt, same agent — the only difference is the skill.
Knowledge base redesign is a big project that touches documentation strategy, information architecture, and team workflows. You'll want to think about: How your current content is organized, what people actually search for vs. browse, whether you have permissions issues, if your page templates are consistent. Different teams need different structures - engineering documentation looks different from marketing. You'd probably benefit from a content audit first, then restructuring. Do you have a Confluence space already? How many pages are we talking? What's your team size?
CONFLUENCE REDESIGN BLUEPRINT SPACE PERMISSION STRUCTURE Root: Engineering Docs (Team access: all engineers, Admins: tech lead + docs owner) ├─ Public Pages (View: all, Edit: docs owner) │ ├─ System Architecture Overview │ ├─ API Reference │ └─ Runbook: Deploy Production ├─ Development Guides (View: engineers only, Edit: authors) │ ├─ Onboarding (canonical source) │ ├─ Local Development Setup │ └─ Testing Procedures ├─ Internal Decisions (View: team, Edit: leads) │ ├─ Architecture Decision Records │ └─ Deprecation Policy └─ Archived (View: team, Edit: none) └─ Old frameworks, deprecated docs PAGE HIERARCHY TEMPLATE Level 1: Root index page (what lives here, how to search) Level 2: Category pages (3-5 related pages per category) Level 3: Detailed how-to pages (single focused task) Level 4: Reference pages (API specs, lookup tables) MACRO USAGE STRATEGY • Status macro: Red/Yellow/Green for "Updated", "Needs Review", "Deprecated" • Expand macro: Hide long reference tables until clicked • Jira macro: Show related tickets/PRs inline • Child pages macro: Auto-generate table of contents from subpages • Database macro: Link to shared data from Google Sheets DISCOVERABILITY FIXES • Search optimization: Every page title includes searchable keyword • Related pages sidebar: Link to 2-3 connected docs • Breadcrumb hierarchy: Show path (Docs > Development > Setup) • Last updated date: Timestamp builds trust (remove stale docs) • Curation boards: Pin top 5 most-read docs per quarter CONTENT GOVERNANCE GOALS: Reduce outdated docs, improve navigation RESPONSIBLE: Docs owner (1 person, 2 hours weekly) RITUAL: Monthly page audit - check 20% of docs for staleness OWNER TAGS: Each doc shows author + last-reviewed date (pressure to update)
About this skill
When a Confluence space passes a few hundred pages, people stop finding things and start asking in Slack. This skill designs a space readers can navigate in two or three clicks, then audits and cleans up what is already there.
What it does
- Sets space purpose, a useful home page, and a page tree no deeper than about three levels
- Builds a small controlled label list and live index pages with Children Display, Content by Label, and Page Properties Report
- Audits stale, orphaned, duplicate, empty, and ownerless pages with CQL queries you can run
- Checks restriction inheritance before any move so pages do not vanish or become exposed
- Plans archive-before-delete with owner sign-off and a governance cadence
What you get
A space plan: proposed tree, label taxonomy, audit findings with evidence and actions, a move and archive plan, and governance. Edition-specific features are marked to verify.
Best for
Engineering, product, and ops teams whose Confluence has sprawled, and anyone setting up a new team space.
SKILL.md preview
---
name: confluence-expert
description: Design or clean up a Confluence space so people can find things - space purpose and home page, a shallow page tree, a label taxonomy, navigation macros (children display, content by label, page properties report), restriction inheritance, and a CQL-driven audit of stale, orphaned, duplicate, and ownerless pages with an archive plan. Use when the user says "our Confluence is a mess", "nobody can find anything in the wiki", "set up a new Confluence space for the team", "restructure our engineering space", "find stale pages", "how should we use labels?", or "what should go on the space home page?".
---
# Confluence Space Architect and Cleanup
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Confluence and Jira Template Builder
Build one Confluence or Jira template people actually fill in: real-example structure, placeholders, roll-up reports, required fields.
Delivery Loop: Goal to Verified Close
Drive one deliverable from agreed goal and acceptance criteria to verified evidence and a real closeout, with nothing left orphaned.
Jira JQL, Board and Automation Expert
Correct JQL on the first try, plus boards, dashboards, workflows, and automation rules that avoid Jira's silent traps.
Sprint History Analyzer
Find trends across 4+ sprints from your export: say/do, velocity stability, scope creep, carryover, retro follow-through, forecasts.