to-issues

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

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill to-issues-kileroppo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/skills/to-issues
Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill to-issues-kileroppo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It breaks a plan, spec, or PRD into independently-grabbable work items so teams can implement end-to-end vertical slices with clear dependencies and predictable progress.

Core Features & Use Cases

  • Tracer-bullet vertical slicing: Produces thin issues that cut through ALL integration layers end-to-end rather than focusing on a single layer.
  • HITL vs AFK granularity control: Marks slices as HITL when human decisions/reviews are required, and prefers AFK slices that can be implemented and merged without interaction.
  • User-guided validation before publishing: Presents a numbered breakdown and asks the user to confirm granularity, dependency relationships, and HITL/AFK labeling before creating tracker issues.
  • Issue tracker publishing in dependency order: Publishes approved issues with a consistent template and “Blocked by” references to ensure proper sequencing.

Quick Start

Use the to-issues skill to break a product plan into tracer-bullet issues by first providing the plan text (or a relevant issue reference) and then asking the skill to produce an approved, dependency-ordered set of issues for the project 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 PRD into actionable issue tracker tickets?

To break a PRD into actionable issue tracker tickets, you provide the plan text to decompose it into independently grabbable work items using tracer-bullet vertical slices. This ensures issues span schema, API, UI, and tests end-to-end for predictable progress.

What is tracer-bullet vertical slicing in project management?

Tracer-bullet vertical slicing in project management is a decomposition technique that produces thin issues cutting through all integration layers end-to-end, rather than focusing on a single layer. This makes each issue independently demoable and verifiable.

How do I plan issue dependencies when decomposing a product spec?

To plan issue dependencies when decomposing a product spec, you propose slice titles and dependency relationships, obtain user approval on the granularity, and then publish issues in dependency order using "Blocked by" references to ensure proper sequencing.

Can I label issues as automated or manual during PRD to tasks conversion?

Yes, during PRD to tasks conversion, you can label issues as HITL when human decisions or reviews are required, and prefer AFK slices that can be implemented and merged without interaction to control workflow granularity.

Does issue decomposition require user validation before publishing tickets?

Yes, issue decomposition requires user-guided validation before publishing tickets. It presents a numbered breakdown and asks the user to confirm granularity, dependency relationships, and HITL or AFK labeling before creating tracker issues.

What are the limitations of vertical slice issue decomposition for roadmap planning?

A limitation of vertical slice issue decomposition is that it requires slices to span schema, API, UI, and tests end-to-end. You must gather conversation context or fetch referenced issues and optionally review the codebase before proposing slices.