skills.rest
JeromyJSmith
JeromyJSmithCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans, specs, or PRDs into dependency-ordered vertical-slice issues.

3|Updated May 11, 2026
Search Tags:#project management#vertical slices#dependency ordering#triage labels#issue breakdown#engineering tickets#product spec decomposition
One-click install
npx skills add https://github.com/JeromyJSmith/lattice-platform --skill to-issues-jeromyjsmith
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill to-issues-jeromyjsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a plan, spec, or PRD into work items that teams can actually implement and verify is time-consuming and often results in horizontal, non-demonstrable tickets.

Core Features & Use Cases

  • Vertical-slice issue breakdown: Converts source material into independently-grabbable issues that cut across all integration layers end-to-end, using tracer-bullet “thin slices.”
  • HITL vs AFK classification: Marks slices as HITL when they require human decisions (e.g., architecture/design review) and prefers AFK for mergeable work without interaction.
  • Dependency-aware publishing: Produces a dependency-ordered, acceptance-criteria-driven set of issues suitable for immediate triage and implementation.
  • Issue-tracker-first workflow: Optionally fetches existing issue context (by number/URL/path) and then drafts, quizzes, and publishes new issues using the provided issue template and label vocabulary.

Quick Start

Ask the assistant to break your plan or PRD into vertical-slice tracer-bullet issues and publish them to the project issue tracker in dependency order.

Frequently Asked Questions about to-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a product spec into vertical slice engineering tickets?▼

HITL and AFK classifications identify which vertical slice issues require human-in-the-loop decisions before proceeding versus which are away-from-keyboard ready for immediate, mergeable implementation without interaction.

How do I order issue dependencies when publishing roadmap items to a tracker?▼

Order issue dependencies when publishing roadmap items by drafting a dependency-ordered set of issues driven by structured acceptance criteria, ensuring slices requiring human decisions are resolved before AFK-ready work is queued for triage.

Can I fetch existing issue context before generating new tickets from a PRD?▼

You can fetch existing issue context by referencing specific issue numbers, URLs, or paths, allowing the breakdown process to draft, quiz, and publish new vertical-slice issues using the provided issue template and label vocabulary.

What is the best way to convert a roadmap idea into actionable engineering tickets?▼

The best way to convert a roadmap idea into actionable engineering tickets is applying tracer-bullet thin slices to create demonstrable, independently-grabbable issues rather than horizontal, non-demonstrable tickets that lack clear verification paths.

Related Skills

Explore More Product & Management Skills→
haryelramalhoharyelramalho

to-issues

Break plans, specs, and PRDs into dependency-ordered project issues.

Community
Intermediate
henrycashe26henrycashe26

to-issues

Break project plans and PRDs into vertical slice issues with acceptance criteria.

Community
Intermediate
yashs33244yashs33244
1

to-issues

Convert plans into dependency-ordered issue tickets with acceptance criteria.

Community
Intermediate
huangzidahuangzida
2

to-issues

Convert project plans, specs, or PRDs into actionable issue tickets.

Community
Advanced