skills.rest
loiane
loianeCOMMUNITY
Explore all skills by this author →
Website𝕏@loianeGitHub

issue-tracker-ingestion

Resolve tracker identifiers via MCP and write ticket metadata into 01-spec.md Source blocks.

50|7|Updated Apr 18, 2026
Search Tags:#mcp#jira#github-issues#azure-boards#tracker-integration#issue-ingestion#01-spec.md
One-click install
npx skills add https://github.com/loiane/specs-driven-development-spring-angular --skill issue-tracker-ingestion
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-tracker-ingestion
Source: https://github.com/loiane/specs-driven-development-spring-angular/tree/main/.windsurf/skills/issue-tracker-ingestion
Command: npx skills add https://github.com/loiane/specs-driven-development-spring-angular --skill issue-tracker-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pulling and validating external ticket details into Spec documents is error-prone and time-consuming. This skill automates capturing ticket metadata from Jira, GitHub Issues, GitHub Pull Requests, Linear, and Azure Boards via MCP and writes a structured Source section into 01-spec.md.

Core Features & Use Cases

  • Resolve: Convert a tracker identifier into an MCP fetch and retrieve a ticket's metadata.
  • Capture: title, description, status, labels, assignee, comments (last 10), attachments (filenames only), URL, and fetched-at timestamp.
  • Output: Write a verbatim Source block in 01-spec.md at the start of the spec so the reference remains accurate.

Quick Start

Run the spec workflow to fetch a ticket and populate 01-spec.md.

Frequently Asked Questions about issue-tracker-ingestion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I pull Jira ticket details into a spec document?▼

You can ingest Jira ticket metadata into a spec by resolving the identifier via MCP, which fetches the title, description, status, and comments, then writes them as a Source block into 01-spec.md.

Can I capture GitHub Issues and Pull Requests into a structured spec?▼

Yes, GitHub Issues and Pull Requests are supported. The skill resolves the ticket identifier via MCP, captures metadata like labels and assignee, and writes a verbatim Source section into your 01-spec.md file.

What's the best way to automate Azure Boards issue ingestion for spec generation?▼

Automating issue ingestion is done by providing an Azure Boards ticket identifier to the skill. It uses MCP to fetch metadata such as attachments and status, then writes a structured Source block at the start of your spec.

Do I need MCP wiring to ingest Linear ticket metadata into specs?▼

Yes, MCP wiring is required to fetch ticket metadata. The skill relies on MCP to retrieve data from trackers like Linear, capture the details, and output a verbatim Source block in the 01-spec.md file.

What ticket metadata is captured when ingesting issues into a spec?▼

The ingestion captures the title, description, status, labels, assignee, recent comments, attachments, URL, and fetched-at timestamp. This metadata is written verbatim as a Source block into 01-spec.md.

How many recent comments are fetched during issue tracker ingestion?▼

The ingestion captures the last 10 comments from the resolved ticket. Along with comments, it fetches the title, status, and attachments, writing them into a Source block in 01-spec.md.

Related Skills

Explore More Software Engineering Skills→
AtharvaN16AtharvaN16

wayfinder

Create shared investigation ticket maps on issue trackers for project management.

Community
Advanced
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate
madebyarismadebyaris
192

sdd-planning

Convert specifications into technical plans with architecture and phased roadmaps.

Community
Basic
HaywardMoriharaHaywardMorihara

jira

View, create, update, and manage Jira issues and sprints via CLI and MCP backends.

Community
Advanced