Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/plan-a-feature-to-confluence
Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it.
Passed 6 of 12 test cases with the skill, and 3 of 12 without it.
and 3 more in the full report
6 fixed7 passed either way12 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are publishing the feature spec 'Payment Gateway V2' and companion files to Confluence space PAY. What exact title should be assigned to the team findings child page?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns the title 'Payment Gateway V2 — Team Findings' to the team findings page. | Missed | Passed |
The instructions your model reads when the skill loads.
bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"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, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
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 create pass: there is no separate relink-and-update pass, and each page is created exactly
once.
The six 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.
Confirm the skill has everything it needs before spending effort producing a plan:
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 theytest cases passed, vs 3 / 12 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.