skills.rest
unnxt30
unnxt30COMMUNITY
Explore all skills by this author →
Website𝕏@unnxt30GitHub

to-issues

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

Updated Jul 17, 2026
Search Tags:#project planning#task breakdown#agile#issue tracking#tickets#prd#vertical slices
One-click install
npx skills add https://github.com/unnxt30/skills --skill to-issues-unnxt30
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/unnxt30/skills/tree/main/to-issues
Command: npx skills add https://github.com/unnxt30/skills --skill to-issues-unnxt30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable tickets is slow and often produces horizontal, layer-by-layer tasks that cannot be shipped independently. This Skill converts planning documents into thin, end-to-end vertical slices published directly to your issue tracker. ## Core Features & Use Cases - Tracer-Bullet Slicing: Breaks work into thin vertical slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable. - HITL vs AFK Classification: Marks each slice as requiring human interaction (HITL) or fully autonomous (AFK), preferring AFK where possible. - Interactive Refinement: Presents the proposed breakdown with titles, dependencies, and user stories, then iterates with you until approved. - Tracker Publishing: Creates issues in dependency order with a structured template covering scope, acceptance criteria, and blockers, plus the correct triage label. - Use Case: After drafting a PRD for a new feature, ask the Skill to break it into issues; it proposes slices, you approve the granularity, and it publishes ready-to-grab tickets to your tracker. ## Quick Start Ask the assistant to break the attached plan or PRD into independently-grabbable issues 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 the conversation and ask for it to be broken into issues. The Skill drafts tracer-bullet vertical slices, lets you review granularity and dependencies, then publishes approved issues to your issue tracker.

What is a vertical slice or tracer-bullet issue?▼

A vertical slice is a thin piece of work 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 this work with any issue tracker?▼

The Skill expects an issue tracker and triage label vocabulary to have been configured beforehand, via the referenced setup command. It publishes issues with the correct triage label unless instructed otherwise.

When should I not split work into vertical slices?▼

Vertical slicing is less suitable when the work is a single-layer change with no end-to-end behavior, such as a pure refactor or documentation update. In those cases a single direct issue is simpler than forcing a slice breakdown.

Related Skills

Explore More Software Engineering Skills→
kagentikagenti

write-a-prd

Interview users and explore codebases to draft structured PRDs.

Official
Advanced
valorisavalorisa
4

create-github-issues

Break down feature plans into vertical slice GitHub issues with dependencies.

Community
Intermediate
OatseOatse

to-prd

Generates a PRD from conversation context and publishes it to the project issue tracker.

Community
Intermediate
mattbutlerengineeringmattbutlerengineering
1

to-issues

Break plans, specs, or PRDs into dependency-ordered vertical-slice issues.

Community
Intermediate