skills.rest
akillness
akillnessCOMMUNITY
Explore all skills by this author →
Website𝕏@akillness0308GitHub

to-issues

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

40|9|Updated Jan 4, 2026
Search Tags:#workflow#planning#issues#decompose#hitl#vertical-slices#afk
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill to-issues-akillness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/to-issues
Command: npx skills add https://github.com/akillness/jeo-skills --skill to-issues-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert plans, specs, or requirements into independently-grabbable vertical slice issues. Each slice is a thin but complete end-to-end cut through all layers (schema, API, UI, tests). Classifies issues as HITL (human-in-the-loop) or AFK (automated, no human interaction needed).

Core Features & Use Cases

  • Vertical-slice decomposition: each slice is end-to-end across schema, API, UI, and tests.
  • HITL or AFK classification to guide human involvement.
  • Tracker-agnostic: works with GitHub Issues, Linear, or any issue tracker, and pairs with to-prd and triage for state management.

Quick Start

Provide a plan or PRD and the skill will decompose it into independently-actionable 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 down a PRD into independently actionable vertical slice issues?▼

To break down a PRD into vertical slice issues, provide the plan or spec. It decomposes requirements into thin, end-to-end slices covering schema, API, UI, and tests for independent implementation.

What are vertical slices in software planning and how do they help issue decomposition?▼

Vertical slices in issue decomposition are thin, complete end-to-end cuts through all layers including schema, API, UI, and tests. They ensure each issue is independently grabbable by AI agents or human developers.

Does this issue decomposition method support GitHub Issues and Linear trackers?▼

Yes, this issue decomposition method is tracker-agnostic and supports GitHub Issues, Linear, or any issue tracker. It classifies issues as HITL or AFK to guide human involvement and integrates with common trackers.

Can I classify decomposed issues for automated AI agents versus human developers?▼

Yes, you can classify decomposed issues for automated AI agents or human developers. The skill categorizes work items as AFK for automated execution or HITL for human-in-the-loop tasks.

What is the best way to prepare feature plans for parallel work items?▼

The best way to prepare feature plans for parallel work items is decomposing them into vertical slices. This creates independently actionable tickets spanning schema, API, UI, and tests for simultaneous development.

Do I need a specific issue tracker to use vertical slice decomposition?▼

No, you do not need a specific issue tracker to use vertical slice decomposition. The skill is tracker-agnostic, working with GitHub Issues, Linear, or any platform while pairing with triage for state management.

Related Skills

Explore More Product & Management Skills→
yash-gargyash-garg

to-issues

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

Community
Intermediate
cstarleacstarlea

github-mcp-orchestrator

Transform user requests into structured GitHub epics with child issues.

Community
Advanced
whyte25whyte25
12

prd-to-issues

Break PRDs into dependency-ordered GitHub issues with vertical slices.

Community
Intermediate
kevinnftkevinnft
13

to-issues

Break plans into tracer-bullet vertical slice issues with acceptance criteria.

Community
Advanced