skills.rest
ttphats
ttphatsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-issues

Breaks plans and PRDs into vertical-slice issues on GitHub or Linear trackers.

Updated Jan 28, 2026
Search Tags:#github#issue tracker#task decomposition#linear#prd#vertical slices#issue breakdown
One-click install
npx skills add https://github.com/ttphats/project-detedxs26 --skill to-issues-ttphats
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/ttphats/project-detedxs26/tree/main/.augment/skills/custom/mattpocock/to-issues
Command: npx skills add https://github.com/ttphats/project-detedxs26 --skill to-issues-ttphats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a plan, spec, or PRD into actionable tracker tickets is slow and often produces horizontal, layer-by-layer tasks that cannot be shipped independently. This Skill converts planning documents into thin, end-to-end vertical slices published directly to your issue tracker. ## Core Features & Use Cases - Tracer-Bullet Slicing: Breaks work into thin vertical slices that cut through schema, API, UI, and tests so each issue is independently demoable. - HITL vs AFK Classification: Labels each slice as requiring human interaction (HITL) or fully autonomous (AFK), with dependency ordering between issues. - Tracker Publishing: Creates issues via GitHub MCP or Linear MCP using a structured template with acceptance criteria and blocker references. - Use Case: After drafting a PRD for a new checkout flow, ask the agent to break it into issues; it proposes slices, confirms granularity with you, then publishes ordered tickets to GitHub. ## Quick Start Ask the agent to break the current plan or PRD into independently-grabbable issues and publish them to the issue tracker.

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

Provide the plan, spec, or PRD in conversation and ask for it to be broken into issues. The Skill drafts vertical slices, asks you to confirm granularity and dependencies, then publishes approved issues to your tracker.

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

A vertical slice is a thin issue that cuts through all layers—schema, API, UI, and tests—rather than one horizontal layer. Each completed slice is independently demoable or verifiable, making it safe for autonomous agents to implement.

Which issue trackers does this Skill support?▼

It publishes issues through GitHub MCP or Linear MCP integrations. If the tracker is not configured, the Skill asks you which tracker type and credentials to use before publishing.

What is the difference between HITL and AFK slices?▼

HITL slices require human interaction, such as an architectural decision or design review. AFK slices can be implemented and merged without human involvement, and the Skill prefers AFK classifications where possible.

Can I adjust the issue breakdown before publishing?▼

Yes. The Skill presents the proposed slices as a numbered list with titles, types, and blockers, then asks about granularity, dependencies, and HITL/AFK labels. It iterates until you approve before publishing anything.

Related Skills

Explore More Product & Management Skills→
codetail-aicodetail-ai

pm

Creates structured PRDs with user stories, acceptance criteria, and scope boundaries.

Official
Advanced
valorisavalorisa
4

create-github-issues

Break down feature plans into vertical slice GitHub issues with dependencies.

Community
Intermediate
claude-office-skillsclaude-office-skills
368

Linear Automation

Automate Linear issue tracking, cycle planning, and GitHub-integrated workflows.

Official
Advanced
paulinett1508-devpaulinett1508-dev

audit-refactor-monolith

Audit monolithic codebases and guide stepwise decomposition to reduce regression risk.

Community
Intermediate