project-documentation-to-confluence

# Project Documentation to Confluence This skill produces project documentation with the core `han-core:project-documentation` skill, lets the user review the result, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the documentation work belongs to `han-core:project-documentation`, and the publishing work belongs to `han-atlassian:markdown-to-confluence`. This skill only validates its inputs, runs the documentation to a temporary file, gets the user's review and publish choice, and hands the file to the publisher. The five steps below are the whole skill. It does not resolve Confluence pages or call the Confluence MCP create/update tools itself; `han-atlassian:markdown-to-confluence` owns all of that. ## Step 1: Validate Inputs Confirm the skill has everything it needs before spending effort producing documentation: 1. **Atlassian MCP reachable (hard requirement).** Call `mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to confirm the server is connected and retrieve the cloud ID(s). If the tool is not available, the call errors, or it returns no accessible resources (typically an authentication or configuration problem), **stop immediately**. Tell the user this skill requires the Atlassian MCP server to be installed, configured, and authenticated, and that they can re-run it once it is connected. Do not fall back to a local-only run; for local-only documentation, point them at `h...