issues

Decompose unstructured product or code dumps into atomic Linear issues.

Updated Jul 31, 2026

Search Tags:#automation #workflow #engineering #backlog #linear #tickets

Ready to run

npx skills add https://github.com/davidsolheim/skills --skill issues-davidsolheim

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/davidsolheim/skills/tree/main/issues
Command: npx skills add https://github.com/davidsolheim/skills --skill issues-davidsolheim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of managing messy, multi-item backlogs by automatically decomposing unstructured brain dumps into atomic, implementation-ready Linear tickets.

Core Features & Use Cases

Intelligent Decomposition: Automatically splits a single user dump into multiple, distinct, and actionable Linear issues.
Contextual Research: Performs a holistic repo investigation to ensure every ticket is grounded in real code evidence and acceptance criteria.
Smart Connectivity: Automatically maps dependencies, identifies duplicates, and clusters related work into epics when appropriate.

Quick Start

Use the issues skill to break down the following list of bugs and feature requests into a set of actionable Linear tickets.

Frequently Asked Questions about issues

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

FAQPage Schema

How do I bulk create Linear issues from an unstructured dump?▼

To bulk create Linear issues from an unstructured dump, decompose the multi-item text into atomic, solve-ready tickets. The process requires Linear API integration to perform board scans, duplicate detection, and final issue creation.

What is the best way to break down a messy backlog into atomic Linear tickets?▼

Breaking down a messy backlog into atomic Linear tickets involves decomposing unstructured product or code dumps into distinct, implementation-ready issues. It applies contextual research to ground each ticket in real code evidence and acceptance criteria.

Can I automatically map dependencies and epics when filing Linear tickets?▼

Yes, you can automatically map dependencies and identify duplicates when filing Linear tickets. The system clusters related work into epics where appropriate, maintaining strict adherence to atomic implementation standards during bulk intake.

Does generating Linear tickets from a brain dump require a Linear API integration?▼

Generating Linear tickets from a brain dump requires a Linear API integration. This connection is necessary to perform board scans for duplicate detection and to execute the actual issue creation within your engineering workflow.

How do I ensure my bulk Linear intake tickets are implementation-ready?▼

To ensure bulk Linear intake tickets are implementation-ready, decompose each item into atomic issues grounded by holistic repo investigation. This guarantees every ticket contains real code evidence and clear acceptance criteria.

When should I avoid using automated bulk ticket filing for Linear?▼

You should avoid using automated bulk ticket filing for Linear when a user message contains only a single distinct task. This approach is specifically designed for multi-item product or code dumps, backlog grooming, and residual ticket filing scenarios.