/investigate-to-confluence

name: investigate-to-confluence
description: >
  Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the
  resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged,
  diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP
  server. Does not investigate to a local file only — use investigate. Does not publish an arbitrary existing markdown
  file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use
  project-documentation-to-confluence. Does not plan or specify a new feature to Confluence — use
  plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.
argument-hint:
  "[symptom or question to investigate] [confluence location: page URL or space + parent] [--mode draft|live (default
  draft)]"
allowed-tools:
  Read, Glob, Grep, Skill, Agent, Bash(find *), mcp__claude_ai_Atlassian__getAccessibleAtlassianResources,
  Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh")

Project Context

• personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"`
• project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""`

As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.

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 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 a local-only investigation, point them at `han-coding:investigate`. This preflight runs first so a missing server fails before any investigation work begins. 2. **A symptom or question to investigate.** Confirm the request names a bug, failure, error, integration, or unexpected behavior to investigate. This — together with any relevant conversation context — is forwarded to `han-coding:investigate` verbatim in Step 2. If the request is too thin to start, let `han-coding:investigate` run its own investigation rather than pre-empting it here. 3. **A Confluence destination.** Confirm the request provides a target location: a **Confluence page URL** (to update that page, or create a child under it), or a **space** (key or name) plus an optional **parent page**. If none was provided, ask for one with `AskUserQuestion`, explaining plainly that the skill needs an exact destination because it does not search Confluence. Do not resolve the page tree here — only confirm a location was given. Carry it through to Step 5; `han-atlassian:markdown-to-confluence` resolves it.

Step 2: Produce the Investigation Report to a Temporary File

Invoke the `han-coding:investigate` skill with the **Skill** tool, **forwarding all provided context** verbatim: the symptom or question, any known reproduction steps or error messages, any suspected entry points, and the relevant conversation context. Do not summarize, trim, or reinterpret the user's context; pass it through so `han-coding:investigate` runs exactly as it would on its own (parallel investigators, conditional specialist analysts, adversarial validation, and the final report) — **except** add two explicit instructions:

• It must write the resulting investigation report to a file under `/tmp/` (for example `/tmp/<symptom-slug>.md`) rather

than into the project's docs or plans directory. This keeps the working report out of the repo until the user decides to publish it, and because the path is explicit input it outranks any `output-directory` the project or personal `.han/config.md` supplies (see [../../references/config-rule.md](../../references/config-rule.md)).

• It must **stop after producing the report**. `han-coding:investigate` normally ends by presenting the plan for

approval