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

atlassian-spec-to-backlog

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically converts Confluence specification documents into structured Jira backlogs with Epics and implementation tickets, ensuring requirements are translated into actionable Jira work items.

Core Features & Use Cases

  • Create Epics first to organize work and link all child tickets
  • Generate and attach implementation tickets (Story/Task/Bug) to the Epic
  • Read Confluence specs and automatically translate requirements into Jira items
  • Use case: an agent converts a Confluence page into a backlog in seconds for sprint planning

Quick Start

Supply the Confluence page URL and the Jira project key to generate the backlog.

Frequently Asked Questions about atlassian-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?▼

Creating Jira backlog items from a Confluence spec requires providing the page URL and Jira project key. The tool reads the specification, establishes Epics, generates child tickets, and outputs a structured backlog summary.

How does converting specs to backlog items work for sprint planning?▼

Converting specs to backlog items works by analyzing a Confluence document, creating parent Epics first, then generating and linking child Stories or Tasks to those Epics. This breaks down requirements into actionable Jira work items for sprint planning.

Can I automatically break down Confluence requirements into Jira implementation tasks?▼

Yes, you can automatically break down Confluence requirements into Jira implementation tasks. The system analyzes the specification page and generates structured child tickets linked to a parent Epic for organized implementation tracking.

What do I need to generate Jira tickets from a Confluence page?▼

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

Does the generated Jira backlog organize implementation tickets under Epics?▼

Yes, the generated Jira backlog organizes implementation tickets under Epics. The system creates the Epic first to establish the work structure, then generates and links all child implementation tickets directly to that Epic.

Is there a summary provided after translating a Confluence spec to Jira issues?▼

Yes, a final backlog summary is provided for review after translating a Confluence spec to Jira issues. This summary outlines the generated Epics and child tickets to verify the requirements were accurately mapped into Jira.

Related Skills

Explore More Software Engineering Skills→
jpoutrinjpoutrin
14

atlassian-attachments

Attach files to Jira issues and Confluence pages via the Atlassian REST API.

Community
Intermediate
SentioLabsSentioLabs
1

spec-to-backlog

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

Official
Advanced
duyle10xba1901duyle10xba1901

pm-skills

Coordinate six Atlassian experts to plan, monitor, and document Jira and Confluence workflows.

Community
Advanced
atlassianatlassian
949

spec-to-backlog

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

Official
Intermediate