Skip to content
TrustedSkillsbeta
Back to all skills

Spec To Backlog

Checked
atlassian·vlatest·productivity·Apache-2.0

Automatically translates detailed software specifications into actionable backlog items, streamlining development and ensuring clear requirements alignment.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add atlassian/atlassian-mcp-server --skill spec-to-backlog -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

atlassian

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned atlassian/atlassian-mcp-server at eb9a5956a7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
eb9a5956a7
Manifest
skills/spec-to-backlog/SKILL.md
Scanned
8 files, 3,188 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The spec-to-backlog skill transforms product specifications into actionable backlog items within Atlassian Jira. It automatically parses specification documents and generates corresponding tasks, stories, or bugs in your Jira project. This streamlines the process of translating high-level requirements into concrete development work.

When to use it

  • New Feature Development: Automatically create Jira issues from detailed feature specifications.
  • Bug Fixes: Convert bug reports with reproduction steps directly into Jira bug tracking entries.
  • Technical Documentation Updates: Translate documentation changes into tasks for technical writers or developers.
  • Sprint Planning: Quickly populate your sprint backlog by importing specification documents.

Key capabilities

  • Jira integration
  • Specification parsing
  • Backlog item generation (tasks, stories, bugs)

Example prompts

  • "Create Jira issues from this product spec: [paste specification text]"
  • "Generate a backlog based on the following requirements document."
  • "Convert this bug report into a Jira issue: [paste bug report details]"

Tips & gotchas

The skill requires access to your Atlassian Jira instance and appropriate permissions to create issues. The quality of generated backlog items depends heavily on the clarity and structure of the input specification documents.