confluence-doclisted

Structure development documents such as designs, definitions, and proposals into readable Confluence pages, render Mermaid natively through a caller-injected diagram macro when one is available (otherwise degrade it to tables/ASCII/Expand), and publish through the Atlassian MCP. Load each document type's section skeleton from the matching file under skeletons/ on demand while using one type-independent engine for input collection, rendering, diagram handling, and publication. The caller injects publication targets (cloudId, space, parent, naming, accounts, status labels, and the optional Mermaid macro identity). Do not generate document content or judge its quality; upstream owns both.
qnamy/harnie · ★ 0 · AI & Automation · score 72

Install: claude install-skill qnamy/harnie

# Confluence Development Documentation (Structure · Degrade · Publish) This skill **does not generate document content.** Upstream architecture and detailed-design methodologies, harnie build steps, tickets, and code own content reasoning. Accept existing context and reorganize it into a Confluence document that other teams can scan at a glance, then publish it. This skill owns the following concerns and their rationale: 1. **What makes a good Confluence document** — Type-specific skeletons and scanability judgments. 2. **Diagram handling** — Render upstream Mermaid natively when the caller injects a Mermaid diagram macro; otherwise degrade Mermaid and verbose prose into tables, ASCII, and panels that do not break in Confluence. 3. **Publication orchestration** — Call the Atlassian MCP. This skill does **not** own the following; the caller (platform layer or routine) injects them: - Publication target: `cloudId`, `spaceId`, `parentId`, page-title rules, author/reviewer account IDs, status-label values, and required reviewers. All are deployment- and environment-specific. - **Publication adapter:** `publicationAdapter.contentFormat` — the writer's body format, **default `"html"`** (the Atlassian MCP HTML+ writer this skill's node forms target and the path verified here). The caller overrides it only for a non-HTML+ writer, and then owns the adapter-specific body/node contract (see the adapter scope under Rendering Rules). - **Mermaid macro (optional):** `mermaidMacro` — t