ticket-intake

Parse Jira issues into structured briefs and numbered requirements lists.

Updated Jul 3, 2026

Search Tags:#automation #planning #requirements #jira #ticket-management #scope-control

Ready to run

npx skills add https://github.com/ohyesgocool/feature-loop --skill ticket-intake-ohyesgocool

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ticket-intake
Source: https://github.com/ohyesgocool/feature-loop/tree/main/skills/ticket-intake
Command: npx skills add https://github.com/ohyesgocool/feature-loop --skill ticket-intake-ohyesgocool

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the ambiguity and scope creep inherent in Jira tickets by distilling complex, multi-comment threads into a single, authoritative, and numbered requirements list that the entire engineering loop can follow.

Core Features & Use Cases

Requirement Extraction: Automatically parses Jira descriptions, comments, and subtasks to identify actionable tasks while filtering out noise.
Chronological Reconciliation: Ensures the latest project decisions supersede older ones, providing a clear audit trail of why requirements changed.
Use Case: Use this when starting a new feature to ensure you are building exactly what the reporter currently wants, rather than what was requested in the original ticket description three weeks ago.

Quick Start

Run the ticket intake skill by providing the Jira ticket key to generate a structured brief and requirements list for your current project.

Frequently Asked Questions about ticket-intake

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

FAQPage Schema

How do I extract actionable requirements from a Jira ticket with multiple comments?▼

To extract actionable requirements from Jira tickets, this skill parses descriptions, comments, and subtasks chronologically to reconcile the latest decisions and generate a structured requirements list.

What is the best way to track scope changes in Jira tickets?▼

Tracking scope changes in Jira tickets is handled by chronologically reconciling comments and subtasks, identifying ambiguous requirements, and establishing a single source of truth for the engineering team.

How do I generate a structured brief from Jira issues before starting development?▼

Generating a structured brief from Jira issues requires providing the ticket key to the skill, which then fetches metadata via Atlassian MCP server integration to output a numbered requirements list.

Do I need an Atlassian MCP server to parse Jira ticket requirements?▼

Yes, an Atlassian MCP server integration is required to fetch Jira issue data and metadata in a read-only, secure manner for parsing into actionable requirements.

Can I use this to filter out noise and identify the latest tasks in Jira subtasks?▼

Yes, this skill automatically parses Jira subtasks and comments to filter out noise, ensuring the latest project decisions supersede older ones for accurate requirement extraction.

Why does my Jira ticket description not match what the reporter currently wants?▼

Jira ticket descriptions often become outdated as decisions shift in comments; this skill reconciles the thread chronologically so the final output reflects the reporter's latest requests.