to-issues

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill to-issues-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill to-issues-thachrocky12345

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: Splits 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 review loop: Presents the proposed breakdown with titles, dependencies, and user stories, then iterates with the user before publishing. - Structured publishing: Creates issues in dependency order with a consistent template (parent, what to build, acceptance criteria, blocked by) and applies the triage label. - Use Case: After drafting a feature spec for a new billing flow, ask the assistant to break it into issues; it proposes six vertical slices, you adjust two dependencies, and it publishes all six tickets with acceptance criteria to the tracker. ## Quick Start Ask the assistant to break the current plan or spec 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 or spec into implementation issues?

Provide the plan, spec, or PRD in the conversation and ask for it to be broken into issues. The Skill drafts vertical slices, lets you review granularity and dependencies, then publishes approved issues to the tracker.

What is a vertical slice or tracer-bullet issue?

A vertical slice is a thin piece of work that cuts through all 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, while AFK slices can be implemented and merged without human involvement. The breakdown prefers AFK slices wherever possible.

Can I review the issue breakdown before anything is published?

Yes. The Skill presents a numbered list of proposed slices with titles, types, blockers, and covered user stories, then iterates on your feedback about granularity and dependencies until you approve.

Does it modify or close the parent issue after publishing?

No. The Skill only creates new issues referencing the parent and explicitly does not close or modify any parent issue. New issues are published in dependency order with the triage label applied.