to-issues

Break plans, specs, or PRDs into dependency-ordered tracer-bullet issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns plans, specs, and PRDs into clear, actionable issue breakdowns that teams can assign, estimate, and deliver without confusion.

Core Features & Use Cases

  • Tracer-bullet slicing: Breaks work into thin vertical slices that span the full delivery path from implementation to verification.
  • Dependency-aware planning: Identifies which issues must land first and which can proceed in parallel.
  • Issue publishing support: Prepares tickets with titles, types, blockers, and acceptance criteria for issue trackers.
  • Use case: A product manager can feed in a feature plan and get a sequenced set of implementation tickets ready for review.

Quick Start

Ask the to-issues skill to break your plan, spec, or PRD into tracer-bullet issues with titles, types, blockers, and acceptance criteria.

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 project issues for a development team?

To break a PRD into actionable project issues, you need to decompose the specification into independently assignable, dependency-ordered tickets. This process creates thin vertical slices spanning implementation to verification, complete with acceptance criteria and blocker mapping.

What is tracer-bullet slicing in project management work breakdown?

Tracer-bullet slicing in work breakdown is a technique that divides a plan into thin vertical delivery slices spanning the full implementation path. It produces dependency-ordered tickets that teams can assign, estimate, and deliver in parallel without confusion.

How do I create dependency-ordered tickets from a feature plan?

Creating dependency-ordered tickets from a feature plan involves analyzing the specification to identify which implementation tasks must land first and which can proceed in parallel. It yields a sequenced set of tracer-bullet issues with ready-to-publish acceptance criteria.

Can I map user stories to implementation tickets for roadmap decomposition?

Yes, you can map user stories to implementation tickets during roadmap decomposition. This classifies work into HITL or AFK categories and produces tracer-bullet issues with titles, types, blockers, and acceptance criteria ready for issue trackers.

What is the best way to prepare implementation tickets for issue trackers?

The best way to prepare implementation tickets for issue trackers is to generate dependency-ordered slices from your spec that include titles, types, blockers, and acceptance criteria. This ensures tickets are ready to publish and assign without manual rework.

Does this work breakdown approach support parallel task assignment?

Yes, this work breakdown approach supports parallel task assignment by applying dependency-aware planning to the specification. It identifies which tracer-bullet issues must land first and which can proceed in parallel, enabling efficient team distribution.