to-issues

Breaks plans, specs, and PRDs into independently-grabbable tracer-bullet issues with blocking dependencies.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/jason23452/my-skill --skill to-issues-jason23452
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/jason23452/my-skill/tree/main/flow/to-issues
Command: npx skills add https://github.com/jason23452/my-skill --skill to-issues-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a large plan, spec, or PRD into actionable work items is error-prone: tasks end up too coarse, dependencies are unclear, and agents cannot work in parallel. This Skill converts planning artifacts into vertical-slice issues that each declare their blockers and can be completed independently. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits work into tracer-bullet issues that cut through schema, API, UI, and tests, each demoable on its own. - Dependency Mapping: Every issue declares which other issues block it, so unblocked work can start immediately and run in parallel. - Granularity Checks: Built-in rules ensure each issue fits one context window, covers at most three acceptance criteria, and has genuine contract-based blockers. - Use Case: After writing a PRD and spec for a new feature, run this Skill to produce a root task.md, per-issue task files, and ADO Task work items written in Traditional Chinese, ready for session-based dispatch. ## Quick Start Break the attached prd.md and spec.md into tracer-bullet issues with blocking dependencies and write them as task files.

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 development tasks?▼

Feed the PRD and related planning artifacts into this Skill, which drafts tracer-bullet vertical slices, checks granularity, and publishes one task file per issue. Each issue declares its blockers so unblocked work can start immediately.

What is a tracer-bullet or vertical-slice issue?▼

A vertical slice is a narrow but complete path through all required layers such as schema, API, UI, and tests. It is demoable or verifiable on its own and sized to fit a single agent session or context window.

How are task dependencies and blockers determined?▼

Each issue lists the other issues that must complete before it can start, based on genuine contracts rather than same-repo ordering. An issue with no blockers can begin immediately, enabling parallel execution.

Can this Skill create Azure DevOps work items directly?▼

The Skill defines the issue content and structure for ADO Task child work items, but actual ADO creation and session dispatch are handled by the Work Coordinator's tools. It does not modify parent PRD or User Story items.

When should I not split an issue further?▼

Avoid splitting when it would create meaningless fragments without unlocking parallelism. Keep an issue whole when it already describes one outcome, fits one session, and has at most three acceptance criteria.