to-issues

Breaks plans and PRDs into vertical-slice issues on the project issue tracker.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill to-issues-pieter-1337
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Pieter-1337/Euricom-tsz/tree/main/.claude/skills/matt-to-issues
Command: npx skills add https://github.com/Pieter-1337/Euricom-tsz --skill to-issues-pieter-1337

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items is slow and often produces horizontal, layer-by-layer tickets that cannot be shipped independently. This Skill converts planning documents into thin, end-to-end vertical slices published directly to the project issue tracker. ## Core Features & Use Cases - Tracer-Bullet Slicing: Breaks plans into thin vertical slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable. - HITL/AFK Classification: Labels each slice as requiring human interaction (HITL) or fully autonomous (AFK), preferring AFK where possible. - Interactive Refinement: Presents the proposed breakdown with titles, types, dependencies, and user stories, then iterates with the user until approved. - Structured Publishing: Publishes issues in dependency order using a consistent template with acceptance criteria and blocker references, applying the correct triage label. - Use Case: After finalizing a PRD for a new feature, ask the assistant to break it into issues; it proposes vertical slices, refines them with you, then creates ready-to-grab tickets on the tracker. ## Quick Start Ask the assistant to break the current plan or PRD into issues using the to-issues skill and publish them to the issue tracker.

Frequently Asked Questions about to-issues

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

FAQPage Schema
How do I break a PRD into implementation issues?

Provide the plan, spec, or PRD in conversation and invoke the skill. It drafts tracer-bullet vertical slices, quizzes you on granularity and dependencies, then publishes approved issues to your issue tracker in dependency order.

What is a vertical slice or tracer-bullet issue?

A vertical slice is a thin issue that cuts through all integration layers end-to-end, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is independently demoable or verifiable.

What is the difference between HITL and AFK slices?

HITL slices require human interaction, such as an architectural decision or design review. AFK slices can be implemented and merged without human involvement, and the skill prefers AFK classifications where possible.

Does the skill modify the parent issue after publishing?

No. The skill references the parent issue in each new issue body but explicitly does not close or modify any parent issue. It only creates new issues with the correct triage label.

When should I not use vertical slice issue breakdown?

Avoid it when work cannot be demoed end-to-end, such as pure infrastructure migrations or research spikes with no user-facing path. The approach assumes each slice delivers a complete, verifiable path through every layer.