skills.rest
yashs33244
yashs33244COMMUNITY
Explore all skills by this author →
GitHub

to-issues

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

1|Updated May 5, 2026
Search Tags:#project planning#acceptance criteria#dependency mapping#technical tickets#vertical slices#issue decomposition#HITL vs AFK
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill to-issues-yashs33244
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/mattpocock/engineering/to-issues
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill to-issues-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates vague, hard-to-track plans by converting them into small, independently-grabbable issue tickets that slice through every integration layer end-to-end.

Core Features & Use Cases

  • Vertical-slice breakdown (tracer bullets): Produces thin issues that each cut through all relevant layers (schema, API, UI, tests) rather than splitting horizontally by component.
  • HITL vs AFK classification: Marks which slices require human interaction (e.g., design/architectural decisions) and which can be implemented and merged without it.
  • Dependency-aware publishing: Generates a dependency-ordered issue set and publishes them with a consistent triage label and acceptance-criteria template.
  • Optional issue-context ingestion: If an existing issue is provided, the Skill fetches and uses its full body and comments to ground the breakdown.

Quick Start

Ask the assistant to convert your plan into vertically sliced issues and publish them to the project issue tracker with clear 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 decompose a PRD into actionable technical tickets?▼

Decompose a PRD into actionable technical tickets by converting it into independently-grabbable issues using end-to-end vertical tracer-bullet slices. This breakdown cuts through all integration layers—schema, API, UI, tests—rather than splitting horizontally by component.

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

Vertical tracer-bullet slices are thin issue tickets that cut through every relevant integration layer end-to-end. This issue decomposition technique ensures each slice delivers a complete, testable path from schema to UI instead of isolating work by individual technical components.

How do I map dependencies when creating issue tickets from a project plan?▼

Map dependencies when creating issue tickets by generating a dependency-ordered issue set from your project plan. The resulting technical tickets are published with a needs-triage label and an acceptance-criteria template, ensuring clear blockers and correct execution order.

Can I use existing issue references to ground project planning and ticket creation?▼

Yes, you can use existing issue references to ground project planning and ticket creation. Providing an existing issue allows the system to fetch its full body and comments, using that context to accurately map dependencies and decompose work into vertical slices.

How do I classify technical tickets for human-in-the-loop versus automated work?▼

Classify technical tickets for human-in-the-loop (HITL) versus away-from-keyboard (AFK) work by marking which vertical slices require human interaction, such as design or architectural decisions, and which can be implemented and merged independently without human intervention.

Do I need acceptance criteria templates for tracker-ready issue tickets?▼

Acceptance criteria templates are required for tracker-ready issue tickets to ensure each vertical slice has clear, testable completion standards. Publishing issues with a consistent template and needs-triage label guarantees actionable tracker items with clear blockers.

Related Skills

Explore More Software Engineering Skills→
johnlindquistjohnlindquist
24

beads

Track tasks and issues with dependency awareness using a Git-backed issue tracker.

Community
Intermediate
amazingloft999-droidamazingloft999-droid
356

to-prd

Creates a PRD from conversation context and publishes it to the issue tracker.

Community
Advanced
Soham407Soham407
1

to-issues

Convert plans, specs, or PRDs into dependency-ordered issue-tracker tickets.

Community
Intermediate
akillnessakillness
40

to-issues

Convert plans, specs, or requirements into vertical slice issues.

Community
Intermediate