headless-enrich-ticket

Gather context and attach structured enrichment documents to issue tracker tickets.

13|1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/unblocked/cookbook --skill headless-enrich-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: headless-enrich-ticket
Source: https://github.com/unblocked/cookbook/tree/main/recipes/headless-enrich-ticket
Command: npx skills add https://github.com/unblocked/cookbook --skill headless-enrich-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Headless ticket enrichment that gathers organizational context and attaches findings to an issue before work begins. Use when an agent should autonomously enrich a Jira, Linear, GitHub, or any issue tracker ticket with related PRs, code paths, historical context, and prior attempts. Two modes: engineering (code-focused) and support (user/product-focused). Does not solve the ticket — only enriches it so whoever picks it up starts with full context.

Core Features & Use Cases

  • Autonomous enrichment of tickets before work begins, gathering related PRs, code paths, historical decisions, and prior attempts.
  • Supports engineering mode (code-focused) and support mode (user/product-focused) to tailor research and enrichment.
  • Produces a structured enrichment document that can be attached to the ticket or consumed by the next assignee for faster context switching.

Quick Start

Trigger the enrichment workflow by supplying the ticket contents or URL to the agent to generate a context-rich brief.

Frequently Asked Questions about headless-enrich-ticket

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

FAQPage Schema
How do I automatically enrich Jira tickets with code paths and related PRs before starting work?

Autonomous ticket enrichment gathers organizational context like related PRs, code paths, and historical decisions, attaching a structured brief to Jira, Linear, or GitHub issues before work begins.

What is the difference between engineering and support modes for issue tracking context research?

Engineering mode focuses ticket enrichment on code paths and technical history, while support mode tailors context research toward user and product-focused information for issue tracking.

Can I use autonomous ticket enrichment to attach historical context to Linear issues?

Yes, autonomous ticket enrichment fetches Linear issue details, gathers historical context and prior attempts via research, and outputs a structured document suitable for direct attachment to the ticket.

Does headless ticket enrichment solve the issue or only gather context for the next assignee?

Headless ticket enrichment does not solve the ticket; it autonomously gathers organizational context and attaches findings so whoever picks it up starts with full context for faster context switching.

What is the best way to prepare a GitHub issue with full context before an engineering workflow begins?

Supply the ticket contents or URL to trigger an autonomous enrichment workflow that generates a context-rich brief, gathering related PRs, historical decisions, and prior attempts for the GitHub issue.

When should I not use autonomous ticket enrichment for my engineering workflow?

You should not use autonomous ticket enrichment when a ticket needs to be solved directly rather than prepped with context, as this process only attaches research findings for the next assignee.