plan-a-feature-to-confluence

## 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. # 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 ...