skills.rest
craft-ts
craft-tsCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

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

3|Updated Jan 9, 2026
Search Tags:#task breakdown#agile#issue tracking#sprint planning#tickets#prd#vertical slices
One-click install
npx skills add https://github.com/craft-ts/craft-ts --skill to-issues-craft-ts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/craft-ts/craft-ts/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/craft-ts/craft-ts --skill to-issues-craft-ts

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 vs AFK classification: Marks each slice as requiring human interaction or safe for autonomous implementation, preferring AFK where possible. - Interactive refinement: Presents the proposed breakdown with titles, types, dependencies, and user stories, then iterates with the user before publishing. - Use Case: After drafting a feature spec for a new checkout flow, run this Skill to produce a dependency-ordered set of tracker issues, each with acceptance criteria and blocker references, ready for AFK agents to pick up. ## 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 plan into issues for my issue tracker?▼

Provide the plan, spec, or PRD in the conversation and invoke the to-issues skill. It drafts vertical slices, asks you to confirm granularity and dependencies, then publishes each approved slice as a tracker issue with acceptance criteria.

What is a vertical slice or tracer-bullet issue?▼

A vertical slice is a thin piece of work that cuts through every layer of the system, such as schema, API, UI, and tests, rather than completing one horizontal layer. Each finished 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 adjust the issue breakdown before anything is published?▼

Yes. The skill presents the proposed slices as a numbered list with titles, types, blockers, and covered user stories, then asks about granularity, dependencies, and merges or splits. Nothing is published until you approve.

Does the skill modify the parent issue after publishing slices?▼

No. The skill explicitly does not close or modify any parent issue. It only references the parent in each new issue body and publishes child issues in dependency order.

Related Skills

Explore More Product & Management Skills→
J0JngJ0Jng
7

to-spec

Synthesizes conversation context into a structured spec published to the project issue tracker.

Community
Intermediate
dayvidphamdayvidpham
2

impl-slice

Coordinate vertical slice planning, worker assignment, and progress tracking.

Community
Advanced
caiohbfurtadocaiohbfurtado

grill-with-docs

Validate project plans against domain models and architectural documentation.

Community
Advanced
maxenergymaxenergy

to-issues

Break plans into tracer-bullet issues with blocker relationships on a tracker.

Community
Advanced