
Confluence Knowledge Architect
Turn Confluence docs into structured decision systems
What You Can Do
You can analyze sprawling Confluence documentation, extract core concepts and relationships, and transform them into structured knowledge systems that inform product strategy and align stakeholders. The skill identifies knowledge gaps, surfaces cross-cutting concerns, and generates artifact templates (decision matrices, dependency maps, requirements trackers) ready for immediate use in planning and governance.
Features
Example Output
Input: 200+ pages of scattered product strategy, API design, and roadmap notes in Confluence
Output:
- π Knowledge Architecture Report
βββ Concept Hierarchy
β βββ Core Domains (5 identified: Auth, Data, Analytics, Integrations, DevEx)
β βββ Cross-cutting Concerns (Security, Performance, Scalability)
βββ Decision Matrix
β βββ 12 major decisions mapped to: owner, impact, status, rationale
βββ Gap Analysis
β βββ Missing docs: API versioning strategy, security threat model, deployment playbook
βββ Stakeholder Alignment
β βββ Consensus summary: 8/10 agreement on OKRs, 3 open trade-offs to resolve
βββ Templates & Checklists (ready to deploy)
βββ RFC review template
βββ Architecture decision record
βββ Roadmap validation checklist
Alternative: Turn raw meeting notes + design docs into a Dependency Graph showing which product decisions block which initiatives β output as an interactive mermaid diagram for engineering and product alignment.
What's Included
- SKILL.md: Complete Claude skill with workflows for documentation analysis, concept extraction, and artifact generation
- Knowledge Extraction Workflow: Step-by-step process for parsing Confluence hierarchies
- Artifact Templates: Decision matrix, traceability matrix, knowledge taxonomy, gap analysis
- Stakeholder Alignment Checklist: Verification steps for consensus and coverage
- Confluence Integration Guide: Instructions for exporting pages and feeding them to Claude
Who It's For
- Product managers β align engineering roadmaps with strategic decisions
- Engineering leaders β audit technical documentation and surface architectural risks
- Enterprise architects β map systems to business capabilities and identify integration gaps
- Documentation teams β assess coverage, identify redundancy, and guide content strategy
- Compliance/governance officers β verify requirements traceability and decision audit trails
Best For
- Documenting and auditing product strategy and architectural decisions
- Preparing for major reviews (board, stakeholder, roadmap planning)
- Merging knowledge bases during team/product consolidation
- Building consensus on complex multi-stakeholder initiatives
- Creating compliance artifacts and audit trails for regulated domains







