to-issues

Break down project plans into vertical slice issue tracker tickets.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill to-issues-herxinsasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/mattpocock-skills/skills/engineering/to-issues
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill to-issues-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down project plans, specs, or PRDs into well-scoped, independently assignable issue tracker tickets is tedious and often leads to poorly structured work items with unclear dependencies and incomplete end-to-end functionality.

Core Features & Use Cases

  • Vertical Slice Issue Creation: Generates thin tracer bullet issues that cut across all integration layers (schema, API, UI, tests) instead of horizontal, layer-only work items, ensuring each ticket delivers a complete, demoable piece of functionality.
  • HITL/AFK Classification: Labels each issue as HITL (requires human input like architectural decisions or design reviews) or AFK (can be implemented and merged without human interaction) to prioritize executable work and flag blockers early.
  • Use Case: Ideal for engineering teams using spec-driven development, this skill turns full product specs, PRDs, or project plans into a prioritized list of well-scoped issues with clear dependency relationships, eliminating manual guesswork in task breakdown.

Quick Start

Provide your project plan, spec, or PRD to the to-issues skill to generate a structured list of vertical slice issues ready to publish to your issue 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 down a product spec into trackable issues for sprint planning?

Vertical slice issue creation generates thin tracer bullet tickets that cut across all integration layers—schema, API, UI, and tests—ensuring each issue delivers a complete, demoable piece of functionality. This prevents poorly structured, layer-only work items that lack end-to-end integration.

How do I classify issues for autonomous work versus human review during task breakdown?

Spec-driven development issue creation applies to new features, bug fix plans, and project roadmap items. It processes full product specs or PRDs to generate well-scoped, independently assignable tickets with clear dependency relationships, eliminating manual guesswork in task breakdown.

What is the best way to structure issue tracker tickets for agile teams?

Vertical slice task breakdown works best for engineering and product teams running spec-driven development workflows. It is ideal when you have a full product spec, PRD, or project plan and need to generate a prioritized list of well-scoped issues ready to publish to your issue tracker.

Why do I end up with poorly scoped work items when creating tickets from a PRD?

Poorly scoped work items often result from manually breaking down PRDs into horizontal, layer-only tickets. Using tracer bullet vertical slice methodology instead generates independently assignable issues with clear dependencies and complete end-to-end functionality, eliminating manual guesswork.