skills.rest
SentioLabs
SentioLabsOFFICIAL
Explore all skills by this author →
GitHub

spec-to-backlog

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

1|Updated Apr 4, 2026
Search Tags:#automation#specification#backlog#jira#confluence#epic#task-breakdown
One-click install
npx skills add https://github.com/SentioLabs/agent-nexus --skill spec-to-backlog-sentiolabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-backlog
Source: https://github.com/SentioLabs/agent-nexus/tree/main/codex-marketplace/plugins/atlassian/skills/spec-to-backlog
Command: npx skills add https://github.com/SentioLabs/agent-nexus --skill spec-to-backlog-sentiolabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Confluence specs are often scattered and hard to translate into concrete Jira work items. This skill automates turning specs into Epics and linked tickets, accelerating backlog creation.

Core Features & Use Cases

  • Create Jira tickets from Confluence pages by deriving an Epic and linked child tickets.
  • Break down a specification into actionable implementation tasks with clear scope.
  • Generate a complete backlog ready for sprint planning, including success criteria references.

Quick Start

Provide a Confluence page URL and your Jira project key to auto-generate an Epic and linked tickets.

Frequently Asked Questions about spec-to-backlog

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

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

To turn a Confluence specification into a Jira backlog, provide the Confluence page URL and Jira project key to auto-generate an Epic with linked child tickets. This converts requirements into actionable implementation tasks ready for sprint planning.

What is the best way to break down Confluence requirements into Jira epics and tasks?▼

The best way to break down Confluence requirements is to analyze the specification page and derive a parent Epic with detailed child tickets linked to it. This ensures clear scope and actionable implementation tasks for the backlog.

Can I automatically generate Jira child tickets linked to an Epic from a Confluence page?▼

Yes, you can automatically generate Jira child tickets linked to an Epic from a Confluence page. The system reads the specification, creates the Epic first, and then generates detailed implementation tasks linked directly to that Epic.

What do I need to create Jira tickets from a Confluence spec?▼

To create Jira tickets from a Confluence spec, you need the specific Confluence page URL and your target Jira project key. These inputs allow the system to read requirements and populate the backlog automatically.

Does converting specifications into Jira issues include success criteria?▼

Yes, converting specifications into Jira issues includes success criteria references within the generated backlog. This ensures the derived Epic and linked child tickets maintain clear scope and alignment with the original requirements.

Related Skills

Explore More Product & Management Skills→
esneiderbravoesneiderbravo
1

spec-to-backlog

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

Community
Advanced
01000001-0100111001000001-01001110
10

jira-workflow

Automate Jira story creation, approvals, and lifecycle transitions via REST API.

Community
Advanced
atlassianatlassian
949

spec-to-backlog

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

Official
Intermediate
SentioLabsSentioLabs
1

atlassian-spec-to-backlog

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

Official
Intermediate