skills.rest
isukharev
isukharevCOMMUNITY
Explore all skills by this author →
GitHub

spec-to-backlog

Convert technical specifications into structured Jira Epics and linked tasks using the atl CLI tool.

5|1|Updated Jun 20, 2026
Search Tags:#automation#project management#specifications#backlog#jira#confluence
One-click install
npx skills add https://github.com/isukharev/atl --skill spec-to-backlog-isukharev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-to-backlog
Source: https://github.com/isukharev/atl/tree/main/plugins/atl/skills/spec-to-backlog
Command: npx skills add https://github.com/isukharev/atl --skill spec-to-backlog-isukharev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual overhead of decomposing complex technical specifications into actionable Jira tickets, ensuring consistent project structure and reducing planning errors.

Core Features & Use Cases

  • Automated Breakdown: Parses Confluence specifications to propose logical Jira Epic and Task structures.
  • Safe Execution: Implements a read-only verification phase before creating any Jira issues to prevent accidental data corruption.
  • Use Case: Use this when you have a new feature design document and need to generate a complete, linked Jira backlog with acceptance criteria and task summaries.

Quick Start

Use the spec-to-backlog skill to analyze the Confluence page with ID 12345 and propose a Jira ticket breakdown for the project KEY.

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?▼

This skill converts Confluence specifications into a structured Jira backlog by parsing the document to propose logical Epic and Task structures. It decomposes requirements into manageable work items complete with summaries and acceptance criteria.

Can I automatically create Jira Epics from an RFC document?▼

You can automatically create Jira Epics from an RFC document using this skill's automated breakdown feature. It parses design documents and RFCs to propose a complete, linked backlog structure ready for issue creation.

Do I need an authenticated atl environment to generate Jira tickets from specs?▼

You need an authenticated atl environment to generate Jira tickets from specs. The skill relies on the atl CLI tool to facilitate the decomposition of requirements and execute the final creation of Jira issues.

What is the safest way to break down technical specifications into Jira tasks?▼

The safest way to break down technical specifications into Jira tasks is using a read-only verification phase. This skill implements a safe execution workflow by proposing the ticket structure first, preventing accidental data corruption before creating issues.

How do I parse a Confluence page to propose a Jira ticket breakdown?▼

To parse a Confluence page to propose a Jira ticket breakdown, you provide the page ID and project key to this skill. It analyzes the Confluence specification and generates a logical Epic and Task hierarchy for the target project.

Related Skills

Explore More Product & Management Skills→
isukharevisukharev
5

search-knowledge

Query Jira and Confluence in parallel to synthesize cited organizational knowledge.

Community
Advanced
grandcamelgrandcamel
42

jira-agile-management

Manage Jira Agile workflows for epics, sprints, backlogs, and story points.

Community
Intermediate
backlinbacklin

atlassian

Automate Jira issue and Confluence content management via REST APIs.

Community
Intermediate
atlassianatlassian
949

spec-to-backlog

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

Official
Intermediate