skills.rest
changfengpro
changfengproCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-issues

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

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

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 the 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/AFK Classification: Labels each slice as requiring human interaction (HITL) or fully autonomous (AFK), with dependency ordering between slices. - Interactive Refinement: Presents the proposed breakdown for user review on granularity, dependencies, and slice merging before publishing. - Use Case: After drafting a PRD for a new feature, ask the agent to break it into issues; it proposes ordered slices, you approve the breakdown, and it publishes labeled, dependency-linked issues to the tracker. ## Quick Start Break this plan 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 conversation and ask for a breakdown into issues. The Skill drafts tracer-bullet vertical slices, quizzes you on granularity and dependencies, then publishes approved issues to the 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 this 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 the parent issue. It only creates new issues with triage labels in dependency order.

When should I not use vertical-slice issue breakdown?▼

Avoid it when work cannot be sliced end-to-end, such as pure infrastructure migrations or research spikes with no demoable path through all layers. In those cases, a single exploratory or chore ticket is more appropriate.

Related Skills

Explore More Product & Management Skills→
ankaboot-sourceankaboot-source
2

to-spec

Synthesizes conversation context into a structured spec and publishes it to the issue tracker.

Official
Intermediate
eduardtomasekeduardtomasek

to-issues

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

Community
Intermediate
arxxyrarxxyr
1

to-prd

Convert conversation context and codebase understanding into a Product Requirements Document and publish it to the issue tracker.

Community
Intermediate
zeshonezeshone

prd-to-issues

Convert PRDs into dependency-ordered GitHub issues with vertical slices.

Community
Advanced