All products

Turn a product spec into Jira tickets with AI

Break a Confluence specification into a proposed epic and implementation tickets, check their scope and create them in the intended Jira project.

To turn a product spec into Jira tickets with AI, focus on work that can be delivered and verified. A delivery feature might require a time selector, fee display and confirmation message, all serving one purpose. The spec-to-backlog guide reads an authorised Confluence document and proposes an epic and a set of related implementation issues.

An issue needs more than a short title. Someone accepting the work should understand what counts as complete and where the underlying requirement came from. An unresolved pricing rule belongs in the open questions rather than becoming an invented acceptance criterion.

What it does

  • Break a specification into implementable pieces
  • Propose a Jira epic for the wider feature
  • Draft acceptance criteria for each item
  • Record dependencies and relevant source context
  • Review the proposed backlog before issue creation

Install and use

  1. Install the skill in a compatible agent, connect Atlassian Rovo MCP and authenticate with permission to read the source Confluence page and create issues in the target Jira project.
  2. Ask “Break this delivery specification into an epic and tickets. Show the acceptance criteria and open questions, then wait for confirmation before creating them.”
  3. Check the project, issue types and scope. After creation, verify the links between the epic, tickets and specification.

FAQ

Source

Made by Atlassian. Original skill: spec-to-backlog, published on GitHub under the Apache-2.0 licence.

View on GitHub