to-issues

Break plans into tracer-bullet vertical slice issues with acceptance criteria.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill to-issues-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/mattpocock/engineering/to-issues
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill to-issues-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break plans, specs, or PRDs into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Core Features & Use Cases

  • Draft vertical slices that span all integration layers end-to-end, ensuring each slice delivers a complete path from schema to UI, API, and tests.
  • Publish issues to the tracker in dependency order with clear blockers and acceptance criteria, enabling iterative refinement and traceability.
  • Align with product goals and ADRs, facilitating triage, estimation, and cross-team coordination.

Quick Start

Break the given plan or PRD into tracer-bullet issues and publish them to the project 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 a PRD into trackable issues for my issue tracker?

Break a PRD into trackable issues by dividing the plan into tracer-bullet vertical slices that span end-to-end integration layers, ensuring each issue delivers a complete path from schema to UI, API, and tests with clear acceptance criteria.

What are tracer-bullet vertical slices in project planning?

Tracer-bullet vertical slices are end-to-end work segments spanning all integration layers from schema to UI. They deliver a complete functional path, ensuring each independently-grabbable issue provides full traceability and iterative refinement.

How do I publish issues to a tracker in dependency order?

Publish issues in dependency order by structuring vertical slices with defined blockers and acceptance criteria. This enables iterative refinement, facilitates triage, and ensures cross-team coordination actions are ready for execution.

Can I use this to break work into end-to-end slices across multiple teams?

Yes, breaking work into end-to-end slices across teams is supported. The process aligns issues with product goals and ADRs, facilitating triage, estimation, and cross-team coordination for ready-to-execute actions.

Does this approach work for converting a spec into implementation tickets?

Yes, converting a spec into implementation tickets is a core use case. The process drafts vertical slices with clear acceptance criteria and blockers, publishing them to the tracker to ensure actions are ready for execution.

What is the best way to ensure issues are independently-grabbable by developers?

Ensure issues are independently-grabbable by drafting tracer-bullet vertical slices that span all integration layers end-to-end. Each slice must deliver a complete path with clear acceptance criteria, blockers, and dependency ordering.