plan-a-feature-to-confluence

Plan a feature specification and publish it to Confluence via Atlassian MCP.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill plan-a-feature-to-confluence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-a-feature-to-confluence
Source: https://github.com/testdouble/han/tree/main/han-atlassian/skills/plan-a-feature-to-confluence
Command: npx skills add https://github.com/testdouble/han --skill plan-a-feature-to-confluence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the end-to-end workflow to plan a feature and publish the resulting specification and artifacts to Confluence, removing manual handoffs and ensuring a consistent page tree in the destination space.

Core Features & Use Cases

  • Orchestrates planning using han-planning:plan-a-feature to produce a feature-specification and companion artifacts in a /tmp workspace.
  • Publishes the generated documentation to Confluence via han-atlassian:markdown-to-confluence, handling a single create pass and cross-link macros.
  • Validates inputs, requires a Confluence destination, and supports publishing as draft or live modes.

Quick Start

Ask the skill to plan a feature and publish to Confluence by providing a feature description and a Confluence destination.

Frequently Asked Questions about plan-a-feature-to-confluence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate publishing a feature specification to Confluence?

The workflow validates inputs, runs a planning step to generate markdown artifacts in a /tmp workspace, rewrites links to Confluence title macros, and publishes the tree via Atlassian MCP in either draft or live mode.

What is the process for generating and posting feature plans to Atlassian Confluence?

It validates your feature description and target space, produces the feature-spec in a /tmp workspace, rewrites internal links to Confluence macros, and publishes the complete page tree in either draft or live mode.

Can I publish feature planning artifacts to Confluence as a draft?

The publishing step uses Atlassian MCP to create the page tree in your chosen mode, handling cross-link macros and artifact creation in a single pass.

Do I need a specific Confluence destination to run an automated feature planning workflow?

Without a validated destination, the orchestration cannot publish the generated feature-specification and companion artifacts via the Atlassian MCP integration.

How are internal links handled when publishing a feature spec to Confluence?

The workflow processes the markdown artifacts from the /tmp workspace and converts links before executing the single-pass markdown-to-Confluence creation.

What limitations exist when automating Confluence page creation for feature plans?

It orchestrates planning and publishing in one run, writing to a /tmp workspace first, so any MCP connection failures or missing destination inputs will halt the end-to-end feature specification workflow.