project-documentation-to-confluence

Generate and publish feature or system documentation to Confluence via Atlassian MCP.

198|19|Updated May 7, 2026

Search Tags:#workflow #documentation #publishing #orchestration #atlassian #confluence

Ready to run

npx skills add https://github.com/testdouble/han --skill project-documentation-to-confluence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-documentation-to-confluence
Source: https://github.com/testdouble/han/tree/main/han-atlassian/skills/project-documentation-to-confluence
Command: npx skills add https://github.com/testdouble/han --skill project-documentation-to-confluence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the manual, error-prone process of creating and publishing feature or system documentation to Confluence by orchestrating content generation and publishing in a single workflow.

Core Features & Use Cases

Orchestrates content generation via han-core:project-documentation for a given feature, system, or component.
Publishes to Confluence through han-atlassian:markdown-to-confluence using a configured Atlassian MCP server.
Validates prerequisites, including Atlassian MCP accessibility and a clear Confluence destination, and coordinates a draft-to-publish workflow.
Use Case: document a new feature and push the documentation to a specific Confluence page or space, automating updates when the feature evolves.

Quick Start

Provide the feature name or doc-path and the Confluence destination to generate and publish the documentation.

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 automate publishing feature documentation to Confluence?▼

To automate publishing documentation to Confluence, provide a feature name or doc-path and a Confluence destination. The workflow validates prerequisites, delegates content generation, publishes the markdown, and returns the published page URL.

What do I need to publish markdown to Confluence using an orchestration workflow?▼

To publish markdown to Confluence, you need a reachable Atlassian MCP server and a clear Confluence destination, specified as a page URL or a space plus parent page, to validate inputs before generating and publishing content.

Can I update existing Confluence pages when a feature evolves?▼

Yes, you can update existing Confluence pages when a feature evolves by specifying the target Confluence page URL. The workflow orchestrates updated content generation and republishes it to the same destination automatically.

Does this documentation workflow require a specific Confluence destination format?▼

The workflow requires a specific Confluence destination format, accepting either a direct page URL or a combination of a space and parent page, ensuring the target location is clear before delegating content generation and publishing.

Why does Confluence documentation publishing fail during validation?▼

Confluence documentation publishing fails during validation if the Atlassian MCP server is unreachable or if the Confluence destination is unclear, preventing the workflow from delegating content creation and publishing tasks.

What is the best way to document a system component and push it to Atlassian Confluence?▼

The best way to document a system component and push it to Atlassian Confluence is using an orchestrated workflow that validates inputs, delegates component documentation generation, and handles markdown-to-Confluence publishing automatically.