skills.rest
pedroscosta
pedroscostaCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans into vertical-slice issues with dependencies and HITL/AFK labels.

35|Updated Apr 30, 2025
Search Tags:#workflow-design#issue-tracking#backlog-management#vertical-slices#tracer-bullet#plan-breakdown
One-click install
npx skills add https://github.com/pedroscosta/live-state --skill to-issues-pedroscosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/pedroscosta/live-state/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/pedroscosta/live-state --skill to-issues-pedroscosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Core Features & Use Cases

Break plans into independently-grabbable issues using vertical slices (tracer bullets). The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Quick Start

Break the plan into tracer-bullet vertical-slice issues and push them to the project issue tracker.

Process

  • Gather context: Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.
  • Explore the codebase (optional): If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.
  • Draft vertical slices: Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.
  • Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.
  • <vertical-slice-rules> - Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones - </vertical-slice-rules>
  • Quiz the user: Present the proposed breakdown as a numbered list. For each slice, show:
    • Title: short descriptive name
    • Type: HITL / AFK
    • Blocked by: which other slices (if any) must complete first
    • User stories covered: which user stories this addresses (if the source material has them)
    • Ask the user: Does the granularity feel right? (too coarse / too fine) Are the dependency relationships correct? Should any slices be merged or split further? Are the correct slices marked as HITL and AFK?
  • Publish: For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise. Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.
  • <issue-template> ... </issue-template> Do NOT close or modify any parent issue.

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 independently-grabbable issues for issue tracking?▼

Break a PRD into independently-grabbable issues by dividing the plan into tracer-bullet vertical slices. Each issue delivers a complete end-to-end path through every integration layer, including schema, API, UI, and tests, rather than a horizontal slice of a single layer.

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

Tracer-bullet vertical slices are narrow implementation paths that cut through all integration layers end-to-end. They ensure each completed issue is demoable or verifiable on its own, prioritizing many thin slices over few thick ones for backlog management.

How do I create implementation tickets that require human interaction versus automated execution?▼

Classify implementation tickets as either HITL (Human-in-the-Loop) or AFK (Away-from-Keyboard). HITL slices require human interaction like architectural decisions, while AFK slices can be implemented and merged without human interaction, preferring AFK where possible.

How do I manage issue dependencies when publishing vertical slices to an issue tracker?▼

Publish vertical slice issues to the issue tracker in dependency order, with blockers first. This allows you to reference real issue identifiers in the "Blocked by" field of subsequent issues to maintain accurate dependency relationships.

Can I convert an existing issue tracker reference into smaller implementation tickets?▼

Yes, you can pass an issue reference like a number, URL, or path as an argument. The system fetches it from the issue tracker, reads its full body and comments, and breaks the plan into vertical-slice implementation tickets without closing or modifying the parent issue.

Related Skills

Explore More Product & Management Skills→
whimzyLivewhimzyLive
3

to-issues

Convert plans and PRDs into actionable issues in project issue trackers.

Community
Intermediate
AgentiveStackAgentiveStack
71

slice

Break a plan into end-to-end vertical slices covering schema, backend, API, UI, and tests.

Official
Intermediate
arxxyrarxxyr
1

to-prd

Convert conversation context and codebase understanding into a Product Requirements Document and publish it to the issue tracker.

Community
Intermediate
maxenergymaxenergy

to-issues

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

Community
Advanced