spec-to-backlog Skill
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements Published by openai in plugins.
Decision snapshot
Is this a fit?
Developers using plugins, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
20 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is spec-to-backlog Skill?
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using plugins
Declared skill metadata
- Source file: plugins/atlassian-rovo/skills/spec-to-backlog/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use spec-to-backlog Skill
- Use it for developers using plugins.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/atlassian-rovo/skills/spec-to-backlog/SKILL.md
What it does
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements
Skill instructions
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
Verified compatibility and discovery
Frequently asked questions
What is spec-to-backlog?
spec-to-backlog is a open-source AI agent skill with Copy skill directory. Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets.
Who is spec-to-backlog best for?
spec-to-backlog is best for reusing agent instructions, scripts, and references.
How do I install spec-to-backlog?
Install or run spec-to-backlog using Copy skill directory. Check spec-to-backlog for the latest setup command.
Is spec-to-backlog actively maintained?
spec-to-backlog may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
