project-documentation-to-confluence

Generates project documentation and publishes it to a specified Confluence location.

Updated Sep 1, 2026
One-click install
npx skills add https://github.com/amirbiron/Han --skill project-documentation-to-confluence-amirbiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-documentation-to-confluence
Source: https://github.com/amirbiron/Han/tree/main/han-atlassian/skills/project-documentation-to-confluence
Command: npx skills add https://github.com/amirbiron/Han --skill project-documentation-to-confluence-amirbiron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing feature or system documentation and then manually publishing it to Confluence involves duplicated effort across tools. This Skill produces project documentation from your codebase and publishes it to a Confluence page or space in one guided workflow, with a review step before anything goes live. ## Core Features & Use Cases - Documentation generation: Delegates to the project-documentation skill to explore the codebase, write the doc, and audit its content, saving the draft to a temporary file. - Controlled publishing: Requires an explicit user choice between saving a Confluence draft, publishing live, or keeping the doc local only. - Use Case: After shipping a new billing component, ask for its documentation to be written and posted under your team's Confluence space; review the generated draft in /tmp, then publish it as a draft page for teammates to edit. ## Quick Start Document the billing service and publish it to the Engineering space in Confluence under the Systems parent page.

Frequently Asked Questions about project-documentation-to-confluence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I publish project documentation to Confluence?▼

Provide a feature or system to document plus a Confluence destination (page URL, or space with optional parent page). The skill generates the documentation to a temporary file, lets you review it, then publishes it as a draft or live page.

What is the difference between project-documentation-to-confluence and markdown-to-confluence?▼

project-documentation-to-confluence generates new documentation from the codebase and then publishes it. markdown-to-confluence only publishes an existing markdown file you already have, without generating any content.

Does publishing to Confluence require an Atlassian MCP server?▼

Yes, a configured and authenticated Atlassian MCP server is a hard requirement. The skill checks connectivity first and stops immediately if the server is unreachable, pointing you to local-only documentation instead.

Can I review the documentation before it goes live on Confluence?▼

Yes, the generated document is written to a /tmp file and shown to you before any publishing. You then explicitly choose to save a Confluence draft, publish live, or keep the file local only.

When should I not use project-documentation-to-confluence?▼

Use project-documentation for local-only docs, markdown-to-confluence for publishing an existing markdown file, and architectural-decision-record or runbook for those specific document types. This skill only covers feature or system documentation destined for Confluence.