skills.rest
ClyptAI
ClyptAIOFFICIAL
Explore all skills by this author →
GitHub

to-issues

Break plans, specs, or PRDs into GitHub issues with vertical slices.

Updated Apr 4, 2026
Search Tags:#workflow#planning#github#issues#breakdown#vertical-slices
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill to-issues-clyptai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/ClyptAI/Clypt-Frontend/tree/main/.agents/skills/mattpocock-skills/to-issues
Command: npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill to-issues-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.

Core Features & Use Cases

  • Break plans into tracer-bullet issues that cut across all integration layers end-to-end.
  • Distinguish between HITL and AFK slices and ensure each slice is complete and demoable.
  • Use for converting roadmaps, PRDs, and high-level plans into implementation tickets that are easy to assign and track.

Quick Start

Provide the source plan or PRD and I will generate starter GitHub issues broken into vertical slices.

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 GitHub issues?▼

To break a PRD into actionable GitHub issues, you provide the source planning document to generate implementation tickets structured as vertical slices. Each issue includes a title, type, blockers, and user story for independent assignment.

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

Tracer-bullet vertical slices are independently-grabbable issues that cut across all integration layers end-to-end. This breakdown ensures each slice is complete, demoable, and distinguishable as either HITL or AFK for effective product planning.

How to convert a high-level plan into implementation tickets for GitHub?▼

Converting a high-level plan into implementation tickets requires applying a structured workflow to create issue-level vertical slices. You supply the plan, and the system generates independently-grabbable tickets with titles, types, and user stories.

Can I use this to create issues for both human-in-the-loop and automated workflows?▼

Yes, you can create issues for both human-in-the-loop (HITL) and away-from-keyboard (AFK) workflows. The breakdown process explicitly distinguishes between HITL and AFK slices to ensure each issue is complete and demoable.

Does the generated issue breakdown include dependencies and blockers?▼

Yes, the generated issue breakdown includes dependencies and blockers. Alongside titles and user stories, the structured workflow explicitly maps blockers to ensure each vertical slice can be tracked and assigned correctly.

What is the best way to structure roadmap items for GitHub issue tracking?▼

The best way to structure roadmap items for GitHub issue tracking is breaking them into tracer-bullet vertical slices. This method creates independently-grabbable tickets that cut across integration layers end-to-end, ensuring each issue is complete and demoable.

Related Skills

Explore More Product & Management Skills→
AmbitionsXXXVAmbitionsXXXV
2

prd-to-plan

Convert a PRD into a phased implementation plan with vertical slices.

Community
Intermediate
raphaelmansraphaelmans

prd-to-issues

Convert PRDs into vertical-slice GitHub issues with dependencies.

Community
Intermediate
truongnattruongnat

to-issues-pro

Decompose PRDs into GitHub issues with vertical slices and HITL or AFK classification.

Community
Advanced
huangzidahuangzida
2

to-issues

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

Community
Advanced