spec-to-backlog

Spec to Backlog

Overview

Transform Confluence specification documents into structured Jira backlogs automatically. This skill reads requirement documents from Confluence, intelligently breaks them down into logical implementation tasks, creates an Epic first to organize the work, then generates individual Jira tickets linked to that Epic—eliminating tedious manual copy-pasting.

Core Workflow

CRITICAL: Always follow this exact sequence:

1. Fetch Confluence Page → Get the specification content
2. Ask for Project Key → Identify target Jira project
3. Analyze Specification → Break down into logical tasks (internally, don't create yet)
4. Present Breakdown → Show user the planned Epic and tickets
5. Create Epic FIRST → Establish parent Epic and capture its key
6. Create Child Tickets → Generate tickets linked to the Epic
7. Provide Summary → Present all created items with links

Why Epic must be created first: Child tickets need the Epic key to link properly during creation. Creating tickets first will result in orphaned tickets.

---

Step 1: Fetch Confluence Page

When triggered, obtain the Confluence page content:

If user provides a Confluence URL:

Extract the cloud ID and page ID from the URL pattern:

• Standard format: https://[site].atlassian.net/wiki/spaces/[SPACE]/pages/[PAGE_ID]/[title]
• The cloud ID can be extracted from [site].atlassian.net or by calling getAccessibleAtlassianResources
• The page ID is the numeric value in the URL path

If user provides only a page title or description:

Use searchConfluence with a CQL query to find the page by title:

searchConfluence(
  cloudId="...",
  cql="type=page AND title ~ '[search terms]'"
)

Do not put CQL into search. The search tool is Rovo semantic search and takes natural language, not query syntax — passing CQL to it will miss the page. Use search only for natural-language discovery (query="one-click checkout spec"), and searchConfluence when you want a title or type filter.