to-issues

Break plans, specs, or PRDs into vertical-slice issues with dependency order.

Updated May 11, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/Commory --skill to-issues-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/IsKenKenYa/Commory/tree/main/.windsurf/skills/to-issues
Command: npx skills add https://github.com/IsKenKenYa/Commory --skill to-issues-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert a plan, spec, or PRD into a set of independently-grabbable issues that can be implemented and merged with clear end-to-end value.

Core Features & Use Cases

  • Vertical-slice breakdown: Produces multiple tracer-bullet issues where each slice cuts through ALL integration layers rather than splitting work horizontally by component.
  • HITL vs AFK planning: Classifies slices as HITL (human-in-the-loop, e.g., architectural decisions or design reviews) or AFK (fully implementable and mergeable without human interaction).
  • Dependency-aware publication: Orders issue creation by blockers and fills “Blocked by” relationships so the tracker reflects the correct execution sequence.
  • User iteration loop: Presents a proposed numbered breakdown and quizzes you to validate granularity, dependencies, and the HITL/AFK labeling before publishing.

Quick Start

Ask the AI: “Break this plan into tracer-bullet issues and publish them to the project issue tracker, using the existing triage labels and dependency order.”

Frequently Asked Questions about to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a tracer-bullet issue in product planning?

A tracer-bullet issue is a vertical slice that cuts through all integration layers—schema, API, UI, and tests—to deliver end-to-end value. It ensures each issue is independently grabbable and mergeable rather than splitting work horizontally by component.

How do I break a PRD into GitHub issues with correct dependency order?

To break a PRD into GitHub issues, the plan is parsed into vertical-slice tickets ordered by blockers. The tracker reflects the correct execution sequence by filling “Blocked by” relationships during publication so dependencies resolve cleanly.

How does HITL vs AFK classification work for issue generation?

HITL vs AFK classification labels issues as human-in-the-loop for architectural decisions or design reviews, versus AFK for fully implementable tickets mergeable without human interaction. This validates granularity and execution context before publishing.

Can I iterate on the vertical-slice breakdown before issues are published to the tracker?

Yes, you can iterate on the vertical-slice breakdown. A proposed numbered breakdown is presented to validate granularity, dependencies, and HITL/AFK labeling, allowing you to adjust the slice structure before any issues are published.

Does issue generation align ticket titles with project glossaries and ADRs?

Yes, issue generation aligns ticket titles and descriptions with the project glossary and ADRs. It fetches referenced issues when provided to maintain consistency with established architectural decisions and terminology.

When should I use vertical-slice issues instead of horizontal component tasks?

Use vertical-slice issues when each ticket must deliver an end-to-end slice across schema, API, UI, and tests. Avoid horizontal component tasks when implementation planning requires independently mergeable units that demonstrate full functional value.