Stats
Actions
Tags
From speckit-extensions
Use when the user wants to create a feature spec from a Jira ticket — e.g. "specify from jira PROJ-123", "/speckit-extensions:specify-from-jira PROJ-123", or "write a spec for <ticket>". Queries the Jira ticket via the Atlassian MCP server and pipes the ticket context into /speckit.specify to produce a feature spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/speckit-extensions:specify-from-jiraThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Pull a Jira ticket and use its content as context for `/speckit.specify`.
Pull a Jira ticket and use its content as context for /speckit.specify.
$ARGUMENTS contains: <jira-ticket-id> [additional-input]
jira-ticket-id (required): Jira issue key, e.g. PROJ-123additional-input (optional): Extra context or instructions to include alongside the ticketExtract the Jira ticket ID (first whitespace-delimited token from $ARGUMENTS) and any additional input (everything after it).
IMPORTANT: Only perform read operations against Jira. Never create, edit, or delete Jira issues, comments, or any other Jira resources.
Using the Atlassian MCP server, retrieve the following for the ticket:
Format the retrieved data into a feature description block:
Jira Ticket: <ticket-id>
Summary: <summary>
Description:
<description>
Acceptance Criteria:
<acceptance criteria, or "N/A" if not present>
Comments:
<author> (<date>): <body>
...
Linked Issues / Subtasks:
- <link-type> <key>: <summary>
...
Append any additional input from $ARGUMENTS after the above block.
Pass the composed context block as the feature description to /speckit.specify.
npx claudepluginhub yesmarket/claude-marketplace --plugin speckit-extensionsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.