investigate-to-confluence

# Investigate to Confluence This skill runs an evidence-based investigation with the core `han-coding:investigate` skill, lets the user review the resulting report, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the investigation work belongs to `han-coding:investigate`, and the publishing work belongs to `han-atlassian:markdown-to-confluence`. This skill only validates its inputs, runs the investigation to a temporary file, gets the user's review and publish choice, and hands the file to the publisher. `han-coding:investigate` produces a **single** report file (the investigation plan: problem statement, evidence summary, root cause analysis, planned fix, validation results, and summary). It does not produce companion artifacts, so this skill publishes that one file as a single Confluence page — the single-page sibling of `han-atlassian:project-documentation-to-confluence`, not the parent-plus-children tree of `han-atlassian:plan-a-feature-to-confluence`. 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 on an investigation: 1. **Atlassian MCP reachable (hard requirement).** Call `mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to confirm the server is connected and ...