spec-to-backlog_skill

Overview

This skill automatically converts Confluence specification documents into structured Jira backlogs. It reads a Confluence page, proposes an Epic and a set of implementation tickets, creates the Epic first, then creates and links child issues, and finally returns a summary with links.

How this skill works

The skill fetches the Confluence page (by URL or search), asks which Jira project to use, and analyzes the spec to derive an Epic-level goal and 3–10 implementation tasks. It presents the planned breakdown for user confirmation, creates the Epic first to capture its key, then creates each child ticket with appropriate issue types and detailed descriptions and acceptance criteria.

When to use it

• You have a Confluence spec and want a ready-to-use Jira backlog without manual copying.
• You need to break a requirements document into actionable implementation tasks.
• You want Epics and child issues created and linked correctly in Jira.
• You want consistent, testable acceptance criteria included in tickets.
• You need to convert multiple spec pages into separate Epics and backlogs.

Best practices

• Provide the Confluence URL or clear page title so the correct page is fetched.
• Confirm the project key before creation so issue types and required fields are validated.
• Review the proposed breakdown and request changes before ticket creation.
• Prefer 3–10 well-scoped tasks per spec to avoid over-fragmentation.
• If the project has custom required fields, supply values when asked to avoid errors.

Example use cases

• Turn a product requirements page into an Epic with Stories for each user-facing feature and Tasks for infrastructure work.
• Convert a bug triage spec into an Epic and several Bug tickets with clear reproduction steps and acceptance criteria.
• Ingest multiple related spec pages and create separate Epics for each major feature.
• Add implementation tickets to an existing Epic by providing the Epic key instead of creating a new one.