to-issues

Break plans into tracer-bullet vertical slice issues across schema, API, UI, and tests.

356|59|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill to-issues-amazingloft999-droid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/amazingloft999-droid/mattpocock-skills/tree/main/skills/engineering/to-issues
Command: npx skills add https://github.com/amazingloft999-droid/mattpocock-skills --skill to-issues-amazingloft999-droid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a plan into independently-grabbable issues using vertical slices (tracer bullets) to enable precise, end-to-end planning and tracking across teams.

Core Features & Use Cases

  • Break work into tracer-bullet vertical slices that span across schema, API, UI, and tests.
  • Classify slices as HITL or AFK and order them by dependencies to unblock downstream work.
  • Publish each slice to the issue tracker using a consistent template to support triage and progress tracking.

Quick Start

Provide your plan or PRD and I will translate it into end-to-end tracer-bullet issues.

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, the skill translates your plan into independently-grabbable vertical slices using tracer bullets. Each slice spans schema, API, UI, and tests to deliver a complete end-to-end path for tracking.

What are tracer-bullet vertical slices in software planning?

Tracer-bullet vertical slices are thin, end-to-end implementation paths cutting across all layers like code, design, tests, and docs. They ensure each tracked issue delivers a functional path rather than isolating tasks by technical layer.

How do I classify and order project issues by dependencies?

You classify and order project issues by labeling each vertical slice as either HITL (Human-in-the-Loop) or AFK (Away-From-Keyboard), then ordering them sequentially to unblock downstream work for precise end-to-end tracking.

Can I use a formal issue template for triage and progress tracking?

Yes, you can use a formal issue template for triage and progress tracking. Each vertical slice is published to the issue tracker using a consistent template that explicitly includes blockers to support effective team triage.

Do I need a complete spec to generate tracked implementation tasks?

You do not need a complete spec to generate tracked implementation tasks; providing a general plan or PRD is sufficient. The tool translates the provided document into end-to-end tracer-bullet issues formatted for your project tracker.