to-issues

Break plans and specs into independently-grabbable vertical-slice issues on the project issue tracker.

Updated May 22, 2026
One-click install
npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill to-issues-viniciuscs84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/viniciuscs84/sdd-toolkit/tree/main/skills/to-issues
Command: npx skills add https://github.com/viniciuscs84/sdd-toolkit --skill to-issues-viniciuscs84

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved 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 or merged independently. This Skill converts a plan into thin tracer-bullet vertical slices and publishes them as ready-to-grab issues on the project issue tracker. ## Core Features & Use Cases - Vertical Slice Breakdown: Splits work into end-to-end tracer-bullet issues that cut through all layers (schema, API, UI, tests) instead of horizontal layer tickets. - HITL/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, types, dependencies, and covered user stories, then iterates with the user until approved. - Issue Publishing: Creates issues in dependency order with a structured template covering parent reference, what to build, acceptance criteria, and blockers, applying the correct triage label. - Use Case: After a spec for a new feature is approved, run this Skill to produce a set of small, independently implementable tracker issues that AFK agents can pick up immediately. ## Quick Start Ask the AI to break the approved plan or spec in the current conversation into vertical-slice 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 plan or spec into implementation issues?

Provide the plan, spec, or PRD in the conversation and the Skill drafts tracer-bullet vertical slices, each cutting through all layers end-to-end. It quizzes you on granularity, dependencies, and HITL/AFK classification before publishing approved issues to the tracker.

What is a vertical slice or tracer-bullet issue?

A vertical slice is a thin but complete path through every layer of the system, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is demoable or verifiable on its own, and many thin slices are preferred over few thick ones.

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 Skill prefers AFK slices wherever possible and asks you to confirm the classification.

Does this Skill modify or close the parent issue?

No, the Skill explicitly does not close or modify any parent issue. It only references the parent in the new issue body when the source material was an existing tracker issue.

What setup is required before creating issues from a plan?

The issue tracker and triage label vocabulary must already be provided, which the Skill notes can be done by running the setup-matt-pocock-skills command. Without that context, issue publishing and labeling cannot proceed correctly.