to-issues

Name: to-issues
Availability: InStock
Author: Prestarius

Convert plans or backlogs into independent tracker issues with acceptance criteria.

1|Updated Jun 9, 2026

Search Tags:#context #backlog #issues #plan #project-management #tracker #epic-numbering

Ready to run

npx skills add https://github.com/prestarius/jet-skills-stack --skill to-issues-prestarius

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a plan, backlog, or work breakdown into independent, self-contained tracker issues that anyone can pick up cold.

Core Features & Use Cases

Read the target's Issue tracker vocabulary and conventions from CONTEXT.md; supports GitHub, Jira, GitLab, Linear, or plain Markdown backlogs.
Reuse existing breakdowns by preserving Epic/User Story/Task structure and applying epic-numbering; carry IDs into each issue as stable references.
Ensure each issue is a grabbable unit of work: title, context, scope, acceptance criteria, labels/estimate, dependencies; with one issue per unit.
Right-size: one issue = one unit of work, not an epic or sub-task.
Output a Markdown set for review and have user confirm before creating in the tracker.

Quick Start

Convert a plan or backlog into a set of independent, ready-to-file tracker issues using the configured tracker vocabulary from CONTEXT.md.

Frequently Asked Questions about to-issues

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

FAQPage Schema

How do I convert a project backlog into ready-to-work tracker issues?▼

To convert a project backlog into tracker issues, the tool reads your plan and tracker configuration from CONTEXT.md, then generates independent issues with titles, context, scope, and acceptance criteria for review before creation.

Does this issue generation tool work with Jira, GitHub, and Linear?▼

Yes, this issue generation tool works with Jira, GitHub, GitLab, and Linear by reading tracker-specific vocabulary from CONTEXT.md to format output issues correctly for your chosen platform.

How does it handle Epic and User Story structures when creating tracker issues?▼

It handles Epic and User Story structures by preserving the existing breakdown hierarchy and applying epic-numbering, carrying original IDs into each generated issue to maintain stable references across the project.

Can I review and edit tracker issues before they are actually created in the tracker?▼

Yes, you can review tracker issues before creation because the tool outputs a reviewable Markdown set containing all proposed issues, requiring your validation and confirmation before filing them in the actual tracker.

What is the right size for a tracker issue when breaking down a work plan?▼

The right size for a tracker issue is one independent, grabbable unit of work rather than an epic or sub-task, ensuring anyone can pick it up cold with clear context, scope, acceptance criteria, and dependencies included.

Why do I need a CONTEXT.md file to generate issues from a plan?▼

You need a CONTEXT.md file to generate issues because it provides the target issue tracker's specific vocabulary and conventions, allowing the tool to accurately format titles, labels, and estimates for your exact project environment.