to-issues

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

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/TrayMachi/dotfiles --skill to-issues-traymachi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/TrayMachi/dotfiles/tree/main/agents/skills/to-issues
Command: npx skills add https://github.com/TrayMachi/dotfiles --skill to-issues-traymachi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable work items is slow and error-prone: teams often create horizontal, layer-by-layer tickets that cannot be demoed 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 every layer (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, types, dependencies, and user stories, then iterates with the user until approved. - Structured publishing: Creates issues in dependency order using a consistent template with acceptance criteria and blocker references, applying the correct triage label. - Use Case: After drafting a PRD for a new feature, ask the agent to break it into issues; it proposes slices, refines them with you, then publishes ready-to-grab tickets to the tracker. ## Quick Start Ask the agent to break the current plan or spec 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 or spec into implementation issues?

Provide the plan, spec, or PRD in the conversation and invoke the skill. It drafts tracer-bullet vertical slices, presents them for your review with dependencies and user stories, then publishes approved issues to the tracker.

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 one horizontal 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.

Can I review the issue breakdown before anything is published?

Yes. The skill presents the proposed slices as a numbered list with titles, types, blockers, and user stories, then asks about granularity, dependencies, and HITL/AFK assignments. Nothing is published until you approve.

Does the skill modify the parent issue after publishing?

No. The skill explicitly does not close or modify any parent issue. It only references the parent in the new issue bodies and publishes child issues in dependency order with the correct triage label.