plan-a-feature-to-confluence

# Plan a Feature to Confluence This skill builds a feature specification with the core `han.planning:plan-a-feature` 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 planning work belongs to `han.planning:plan-a-feature`, and the publishing work belongs to `han.atlassian:markdown-to-confluence`. This skill only validates its inputs, runs the planning skill to a temporary folder, gets the user's review and publish choice, and hands each file to the publisher. `han.planning:plan-a-feature` produces a small **set** of files — the primary `feature-specification.md` plus companion artifacts under `artifacts/` (the decision log, the team findings, and a lazily-created technical-notes file). This skill publishes the **spec as a parent page** and each companion artifact as a **child page** beneath it, so the whole plan lands in Confluence as one small page tree. The files cross-reference each other with relative links that do not resolve once each file is its own Confluence page. Because this skill decides every page's title up front, it rewrites those cross-file links into Confluence **title-based page-link macros** (the `<ac:link><ri:page ri:content-title="..."/>…</ac:link>` form; Step 5 gives the exact macro to emit, link body and all) before creating any page — these resolve by title at view time, so no page URL or ID has to exist first. That collapses publishing to a **single c...