skills.rest
koseki2580
koseki2580COMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans, specs, or PRDs into dependency-ordered issue tracker tickets.

Updated Apr 30, 2026
Search Tags:#project management#GitHub issues#vertical slices#issue decomposition#triage labels#HITL vs AFK
One-click install
npx skills add https://github.com/koseki2580/skills --skill to-issues-koseki2580
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/koseki2580/skills/tree/main/skills/to-issues
Command: npx skills add https://github.com/koseki2580/skills --skill to-issues-koseki2580

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the ambiguity and rework of translating a plan, spec, or PRD into actionable engineering tasks by producing issue-ready vertical slices.

Core Features & Use Cases

  • Tracer-bullet vertical slice breakdown: Converts requirements into narrow, end-to-end issues that cut through schema, API, UI, and tests instead of horizontal layer work.
  • Dependency-aware HITL/AFK structuring: Marks slices as HITL when human decisions are required and AFK when they can be implemented and merged without blocking review.
  • Issue tracker publishing with triage labels: Drafts an acceptance-criteria-based issue template and publishes slices in dependency order with consistent triage labeling.
  • Use case: You have a PRD for a new feature and need to transform it into independent GitHub issues so multiple agents can implement in parallel while maintaining real integration progress.

Quick Start

Ask the AI to use the to-issues skill to convert your plan or PRD into tracer-bullet issues, quiz you on granularity and dependencies, then publish the approved slice issues to your issue tracker with the needs-triage label.

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 vertical slices for GitHub issues?▼

To break a PRD into vertical slices for GitHub issues, convert requirements into narrow, end-to-end tracer-bullet cuts through schema, API, UI, and tests rather than horizontal layers. This creates independently-grabbable tickets showing real integration progress.

What is the best way to structure dependency-aware issues for parallel agent implementation?▼

The best way to structure dependency-aware issues is marking slices as HITL when human decisions are required and AFK when implementation can merge without blocking review. Publishing in dependency order ensures multiple agents can implement in parallel without integration conflicts.

How do I publish GitHub issues with acceptance criteria and triage labels?▼

Publish GitHub issues with acceptance criteria by drafting a template-based issue structure and applying consistent triage labeling like needs-triage. This ensures each vertical slice has clear, testable boundaries and enters the tracker ready for prioritization.

Can I use tracer-bullet vertical slice decomposition for both feature planning and PR intent translation?▼

Yes, tracer-bullet vertical slice decomposition applies to feature planning, PRD breakdown, and translating PR intent into implementation-ready work packages. It produces actionable engineering tasks for both HITL and AFK slices regardless of the source document.

Why does converting a spec into actionable engineering tasks eliminate rework?▼

Converting a spec into actionable engineering tasks eliminates rework by removing ambiguity through end-to-end tracer-bullet slices. Each issue cuts through all integration layers, ensuring the package is implementation-ready and satisfies dependency ordering and acceptance-criteria completeness.

What are the limitations of using vertical slices for issue tracker publishing?▼

A limitation of using vertical slices for issue tracker publishing is the need to accurately identify HITL versus AFK boundaries. Misjudging this dependency structuring can cause workflow blocking, requiring careful granularity quizzing before publishing approved slice issues.

Related Skills

Explore More Product & Management Skills→
kartikkabadikartikkabadi

to-issues

Break plans, specs, or PRDs into dependency-ordered issues with acceptance criteria.

Community
Advanced
fray-cloudfray-cloud

prd-to-issues

Break a PRD into dependency-ordered GitHub issues using tracer-bullet vertical slices.

Community
Intermediate
babuallybabually
1

to-issues

Break plans, specs, and PRDs into actionable issue tracker tickets.

Community
Advanced
oakossoakoss
14

tracer-bullets

Implement features as verified vertical end-to-end slices across application layers.

Official
Intermediate