to-issues

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

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill to-issues-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill to-issues-brandtam

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 or safe for autonomous implementation, and publishes with the correct triage label. - Interactive review loop: Presents the proposed breakdown with titles, types, dependencies, and covered user stories, then iterates with you before publishing. - Use Case: After drafting a PRD for a new feature, ask the agent to break it into issues; it proposes dependency-ordered slices, you approve the granularity, and it publishes ready-to-grab tickets to the tracker. ## Quick Start Ask the agent 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 plan or 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, quizzes you on 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 the skill publish issues automatically without review?▼

No. It first presents the proposed breakdown as a numbered list with titles, types, blockers, and covered user stories, then iterates with you on granularity and dependencies until you approve before publishing.

What setup is required before creating issues from a plan?▼

The issue tracker and triage label vocabulary must be configured beforehand, via the referenced setup command. Without that configuration the skill cannot publish issues with the correct triage labels.