skills.rest
atlassian
atlassianOFFICIAL
Explore all skills by this author →
WebsiteGitHub

spec-to-backlog

Convert Confluence specification documents into structured Jira backlogs with Epics and linked tickets.

949|119|Updated Aug 1, 2025
Search Tags:#requirements#specifications#backlog#Jira#task creation#Confluence#epic
One-click install
npx skills add https://github.com/atlassian/atlassian-mcp-server --skill spec-to-backlog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-backlog
Source: https://github.com/atlassian/atlassian-mcp-server/tree/main/skills/spec-to-backlog
Command: npx skills add https://github.com/atlassian/atlassian-mcp-server --skill spec-to-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Product managers and engineers spend hours manually converting detailed specification documents into structured Jira Epics and tasks. This tedious, error-prone process often delays project kick-off and introduces inconsistencies. This skill automates the entire breakdown and creation process.

Core Features & Use Cases

  • Automated Backlog Creation: Read Confluence specification documents and automatically generate a hierarchical Jira backlog, including a parent Epic and linked child tickets.
  • Intelligent Task Breakdown: Decompose high-level requirements into actionable tasks, assigning appropriate Jira issue types (Story, Task, Bug) based on content.
  • Contextual Descriptions: Ensure each created ticket includes relevant context, requirements, and acceptance criteria derived directly from the specification.
  • Use Case: A product manager finishes a detailed Confluence spec for a new feature. Instead of spending a day creating Jira tickets, they use this skill to instantly generate the entire backlog, complete with an Epic and linked implementation tasks, ready for sprint planning.

Quick Start

Convert the Confluence page 'New Feature Spec' into a Jira backlog in the 'PROJ' project. Generate Jira tickets from this Confluence URL: https://yoursite.atlassian.net/wiki/spaces/PRODUCT/pages/123456/New+Feature+Spec

Frequently Asked Questions about spec-to-backlog

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

FAQPage Schema
How do I convert a Confluence specification into a Jira backlog automatically?▼

Converting specifications to Jira backlogs involves reading your Confluence spec document, analyzing requirements, creating a parent Epic, and generating linked child tickets. This skill automates the entire process end-to-end, transforming detailed specs into structured, ready-to-plan backlogs in minutes instead of hours.

Can I create Jira Epics and tasks directly from Confluence pages?▼

Yes. This skill reads Confluence specification pages, intelligently breaks down high-level requirements into actionable tasks with appropriate Jira issue types—Story, Task, Bug—and creates a parent Epic with all child tickets linked and contextualized from your spec content.

What's the best way to avoid manual ticket creation when managing product requirements?▼

Automating backlog creation from specifications eliminates the tedious manual breakdown. By converting Confluence specs directly to hierarchical Jira backlogs with Epics and implementation tickets, you reduce errors, maintain consistency, and accelerate sprint planning.

Do I need to manually add acceptance criteria and context to each Jira ticket?▼

No. The skill extracts relevant context, requirements, and acceptance criteria directly from your Confluence specification document, embedding them into each generated ticket so every issue has the context needed for implementation.

Can this work with detailed feature specifications in Confluence?▼

Yes. This skill is designed specifically for Confluence specification documents containing feature details and requirements. It reads these pages, decomposes complex specs into structured task hierarchies, and outputs a complete Epic-based backlog.

What issue types does the skill assign when breaking down requirements?▼

The skill intelligently analyzes specification content and assigns appropriate Jira issue types—Story, Task, or Bug—based on requirement type. This ensures your backlog uses correct issue classifications aligned with your workflow from the start.

Related Skills

Explore More Product & Management Skills→
Knuckles-TeamKnuckles-Team

spec-to-backlog

Convert Confluence specifications into Jira Epics and linked tickets.

Official
Intermediate
atlassianatlassian
949

spec-to-backlog

Convert Confluence specification documents into structured Jira backlogs with Epics and linked tickets.

Official
Intermediate
dieu-donneedieu-donnee

atlassian-mcp

Automate Jira and Confluence workflows via the MCP protocol.

Community
Advanced
SentioLabsSentioLabs
1

spec-to-backlog

Converts Confluence specifications into linked Epic and Jira tickets for backlog creation.

Official
Advanced