skills.rest
hgxszhj
hgxszhjCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans, specs, or PRDs into tracer-bullet issues on a project tracker.

Updated May 7, 2026
Search Tags:#workflow#template#planning#triage#issue-tracker#vertical-slices
One-click install
npx skills add https://github.com/hgxszhj/mattpocock_skills --skill to-issues-hgxszhj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/hgxszhj/mattpocock_skills/tree/main/skills/engineering/to-issues
Command: npx skills add https://github.com/hgxszhj/mattpocock_skills --skill to-issues-hgxszhj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts project plans, specifications, or PRDs into independently-grabbable issues on your project tracker by using tracer-bullet vertical slices.

Core Features & Use Cases

  • Draft vertical slices that deliver end-to-end coverage across all integration layers (schema, API, UI, tests).
  • Publish issues to the tracker in dependency order, with a clear blocker graph and an end-to-end acceptance path.
  • Use a structured issue template to ensure consistency and traceability across iterations.

Quick Start

Run /setup-matt-pocock-skills to configure your tracker and triage vocabulary, then provide a plan to convert into 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 slices for my tracker?▼

To break a PRD into actionable issue slices, you draft end-to-end vertical slices covering schema, API, UI, and tests, then publish them to your issue tracker in dependency order with a clear blocker graph.

What are tracer-bullet vertical slices in issue planning?▼

Tracer-bullet vertical slices are end-to-end issue units that deliver coverage across all integration layers, ensuring each slice delivers a thin working path through the architecture rather than focusing on horizontal layers.

Do I need a configured issue tracker to generate vertical slice issues?▼

Yes, you need a configured issue tracker, a shared triage vocabulary, and a standard issue-template to ensure consistent traceability before converting plans into independently-grabbable issues.

How to publish issues in dependency order from a project specification?▼

You publish issues in dependency order by mapping the blocker graph from your drafted vertical slices, ensuring each published issue traces back to the spec through a structured template.

Does this issue conversion workflow require any external dependencies?▼

No external dependencies are required, but you must run a setup process to configure your tracker and establish a shared vocabulary before generating issues from your plans.

Can I use this to convert specs into issues without a standard issue template?▼

No, a standard issue-template is required to ensure consistent traceability across iterations when converting specs into independently-grabbable issues on your project tracker.

Related Skills

Explore More Software Engineering Skills→
dallenpyrahdallenpyrah

setup-matt-pocock-skills

Configure repository issue trackers, triage labels, and domain documentation layouts.

Community
Intermediate
xenitV1xenitV1
230

backend-design

Enforce backend design patterns for scalable systems with vertical slice architecture.

Community
Advanced
yash-gargyash-garg

to-issues

Break product plans into dependency-aware issue tracker tasks with acceptance criteria.

Community
Intermediate
ayehiaaayehiaa

to-issues

Breaks a plan into dependency-ordered, tracer-bullet vertical-slice issues.

Community
Advanced