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.zipInstalls 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.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
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
| Source | MCP server | Identifier shape |
|---|---|---|
| Jira (Atlassian) | atlassian | SHOP-1422 |
| GitHub Issues | github | owner/repo#42 or URL |
| GitHub Pull Requests | github | owner/repo!42 or URL |
| Linear | linear | ENG-123 |
| Azure Boards | azure-devops | AB#54321 |
If no MCP is configured, fall back to user-provided text. Never invent a ticket.
Recipe (per source)
-
Resolve identifier → MCP fetch.
-
Capture: title, description, status, labels, assignee, comments (last 10), attachments (filenames only), URL, fetched-at timestamp.
-
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. -
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 Questionsas aQ-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-NNNfor 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
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| issue-tracker-ingestion (this skill) | 0 | 3mo | No flags | Beginner |
| spec-kit-workflow | 11 | 7mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| linear-ticket | 1 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by loiane
View all by loiane →You might also like
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
manage-issues
momics
Create, update, and close GitHub issues on Momics/iroh-http. USE FOR: filing bugs or feature requests, closing issues with commit links, triaging issues with labels and priority. Ensures consistent structure (Summary, Evidence, Impact, Remediation, Acceptance criteria) and correct label usage. DO NO
tpp
photostructure
Work on a Technical Project Plan. Use when starting or continuing work on a TPP from _todo/.
prd
alfredolopez80
Product Requirements Document generation and management with INVEST-compliant user stories