skills.rest
vessux
vessuxCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Break plans, specs, or PRDs into independent issue tickets with tracer-bullet vertical slices.

1|Updated May 20, 2025
Search Tags:#planning#agile#project-management#issue-tracker#vertical-slices#tracer-bullet#to-issues
One-click install
npx skills add https://github.com/vessux/dotfiles --skill to-issues-vessux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/vessux/dotfiles/tree/main/umbel/skills/pocock/to-issues
Command: npx skills add https://github.com/vessux/dotfiles --skill to-issues-vessux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Core Features & Use Cases

  • Drafts tracer-bullet vertical slices that cover end-to-end workflows across all integration layers (schema, API, UI).
  • Classifies slices as HITL or AFK to balance human oversight with automation-ready work.
  • Publishes issues to the tracker in dependency order with clear blockers and aligned user stories.

Quick Start

Provide a numbered list of tracer-bullet vertical slices with titles, types (HITL/AFK), blockers, and mapping to user stories for the given plan.

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 into actionable issues for an agile project tracker?▼

To break a PRD into actionable issues, you draft tracer-bullet vertical slices that cover end-to-end workflows across schema, API, and UI layers, then publish them to your tracker in dependency order with clear blockers.

What are tracer-bullet vertical slices in project management?▼

Tracer-bullet vertical slices are independently-grabbable issue tickets that cut end-to-end across all integration layers, ensuring each slice delivers a complete workflow rather than isolating horizontal technical layers.

How to classify issue tickets as HITL or AFK for development workflows?▼

You classify issue tickets as HITL (human-in-the-loop) or AFK (away-from-keyboard) during the slicing process to balance human oversight with automation-ready work when drafting vertical slices from your plan.

Can I use this approach to map user stories to dependency-ordered issue tickets?▼

Yes, you can map user stories to dependency-ordered issue tickets. The process aligns each tracer-bullet vertical slice with specific user stories and publishes them with clear blockers to prepare issues ready for tracker publishing.

When do I need vertical slices instead of horizontal tasks for issue tracking?▼

You need vertical slices when your product development workflows require end-to-end coverage across multiple layers like schema, API, and UI, ensuring each independently-grabbable issue delivers functional value rather than isolated technical components.

Does to-issues work for splitting specs that require multi-layer integration?▼

Yes, to-issues works for splitting specs requiring multi-layer integration by drafting complete vertical slices that span schema, API, and UI, assessing dependencies, and preparing issues ready for tracker publishing.

Related Skills

Explore More Product & Management Skills→
MADTeacherMADTeacher

prd-to-vertical-slice-tasks

Decompose plans and PRDs into vertical slice tasks with dependencies and acceptance criteria.

Community
Advanced
brandtambrandtam

to-issues

Breaks down project plans into end-to-end tracer-bullet issue slices.

Community
Intermediate
SwitchbackTechSwitchbackTech
228

to-issues

Convert plans into linked issues with acceptance criteria and blockers.

Official
Advanced
cagdotincagdotin
36

to-issues

Break down plans, specs, or PRDs into tracer-bullet issues for project trackers.

Community
Intermediate