skills.rest
Oatse
OatseCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

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

Updated May 23, 2026
Search Tags:#planning#issue tracker#task decomposition#tickets#prd#vertical slices#issue breakdown
One-click install
npx skills add https://github.com/Oatse/CWE-Automation --skill to-issues-oatse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Oatse/CWE-Automation/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/Oatse/CWE-Automation --skill to-issues-oatse

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 breaks work into thin vertical slices and publishes them as ready-to-grab issues on your issue tracker. ## Core Features & Use Cases - Tracer-bullet slicing: Splits a plan into end-to-end vertical slices that cut through schema, API, UI, and 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 refinement: Presents the proposed breakdown with titles, types, dependencies, and user stories, then iterates with you until approved. - Tracker publishing: Creates issues in dependency order using a structured template with acceptance criteria and blocker references, applying the correct triage label. - Use Case: After drafting a feature spec for a new billing flow, run this Skill to produce six independently-grabbable issues, each with acceptance criteria and explicit blocker links, ready for AFK agents to implement. ## Quick Start Break the attached feature spec 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 invoke the Skill. It drafts tracer-bullet vertical slices, quizzes you on granularity and dependencies, then publishes approved slices as issues with acceptance criteria.

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

A vertical slice is a thin but complete path through every layer of the system, including schema, API, UI, and tests. Unlike horizontal layer-by-layer tasks, each slice is independently demoable and verifiable on its own.

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 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 and publishes child issues in dependency order with the correct triage label.

When should I not use vertical-slice issue breakdown?▼

Avoid it for trivial single-file changes where slicing adds overhead, or when the issue tracker and triage label vocabulary have not been configured. Run the referenced setup command first if tracker context is missing.

Related Skills

Explore More Product & Management Skills→
kagentikagenti

write-a-prd

Interview users and explore codebases to draft structured PRDs.

Official
Advanced
eduardtomasekeduardtomasek

to-issues

Converts plans and PRDs into vertical-slice issues on a project issue tracker.

Community
Intermediate
kos3nzkos3nz

setup-matt-pocock-skills

Configure per-repo agent scaffolding for issue tracking, triage labels, and domain docs.

Community
Intermediate
MichaelSolatiMichaelSolati

to-issues

Break down project plans, specs, and PRDs into structured vertical-slice issues.

Community
Intermediate