IS

issue-tracker-ingestion

Automates pulling issue or PR descriptions into spec files.

Install

mkdir -p .claude/skills/issue-tracker-ingestion && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19362" && unzip -o skill.zip -d .claude/skills/issue-tracker-ingestion && rm skill.zip

Installs to .claude/skills/issue-tracker-ingestion

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Pull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Use at the start of `/spec` whenever the user references an external ticket.
194 charsno explicit “when” trigger
Beginner

Key capabilities

  • Fetch issue details from Jira, GitHub, Linear, or Azure Boards
  • Format ticket metadata into a standard specification section
  • Extract acceptance criteria from verbatim ticket text
  • Track updates to tickets in technical specifications

How it works

The skill resolves a ticket identifier via MCP, captures metadata like title and status, and writes it into a specific section of a specification file. It strictly uses verbatim text for requirements and acceptance criteria.

Inputs & outputs

You give it
Issue tracker identifier or URL
You get back
Formatted ## Source section in 01-spec.md

When to use issue-tracker-ingestion

  • Starting a new technical spec from a Jira ticket
  • Syncing requirements from GitHub issues to documentation
  • Verifying spec details against Linear tickets
  • Extracting acceptance criteria from task trackers

About this skill

Issue tracker ingestion

Supported sources

SourceMCP serverIdentifier shape
Jira (Atlassian)atlassianSHOP-1422
GitHub Issuesgithubowner/repo#42 or URL
GitHub Pull Requestsgithubowner/repo!42 or URL
LinearlinearENG-123
Azure Boardsazure-devopsAB#54321

If no MCP is configured, fall back to user-provided text. Never invent a ticket.

Recipe (per source)

  1. Resolve identifier → MCP fetch.

  2. Capture: title, description, status, labels, assignee, comments (last 10), attachments (filenames only), URL, fetched-at timestamp.

  3. Write a verbatim block in 01-spec.md:

    ## Source
    
    - **System:** Jira
    - **ID:** SHOP-1422
    - **URL:** https://example.atlassian.net/browse/SHOP-1422
    - **Title:** Apply gift card at checkout
    - **Status:** In Progress
    - **Fetched:** 2026-04-18T10:00:00Z
    
    ### Description (verbatim)
    > Users should be able to apply a gift card during checkout. It should reduce the order total. If the card has been used, show an error.
    
    ### Comments (last N, verbatim)
    > [PM, 2026-04-15]: Confirmed only authenticated buyers in scope.
    > [Eng lead, 2026-04-16]: Use existing error envelope.
    
  4. Extract candidate ACs only from the verbatim text. Do not paraphrase requirements; quote the source line and put your AC under it. If a candidate AC has no source line, it goes to ## Open Questions as a Q-NNN.

No-invention enforcement

If a source field is missing (e.g. no acceptance criteria in the ticket), the agent does not fill it from imagination. It writes:

- **Q-001** — Source ticket has no explicit acceptance criteria. Need user to confirm AC list before proceeding to AC drafting.

/spec then halts and asks the user.

Updating after the ticket changes

If the user re-runs /spec and the ticket has changed:

  • Re-fetch.
  • Diff old vs new in ## Out-of-Band Inputs ("ticket updated 2026-04-19; description gained paragraph about partial redemption").
  • Add Q-NNN for any new requirement not yet in AC.

Anti-patterns

  • "The ticket says X" without quoting it.
  • Summarizing comments instead of quoting.
  • Pulling AC from the ticket title alone.
  • Silently ignoring an unread comment that contradicts the description.
  • Assuming the ticket assignee = the spec author.

When not to use it

  • When no MCP server is configured and no text is provided
  • When attempting to invent acceptance criteria

Prerequisites

Configured MCP server for the target issue tracker

Limitations

  • Requires explicit user confirmation if acceptance criteria are missing
  • Does not support paraphrasing requirements

How it compares

It mandates a verbatim-only approach to requirements extraction, preventing the common anti-pattern of paraphrasing or inventing acceptance criteria.

Compared to similar skills

issue-tracker-ingestion side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
issue-tracker-ingestion (this skill)03moNo flagsBeginner
spec-kit-workflow117moNo flagsIntermediate
product-manager-toolkit327moReviewBeginner
linear-ticket16moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry