to-issues

Break project plans and PRDs into assignable vertical slice issues.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/a35506322/Lab.Todo --skill to-issues-a35506322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/a35506322/Lab.Todo/tree/main/.cursor/skills/to-issues
Command: npx skills add https://github.com/a35506322/Lab.Todo --skill to-issues-a35506322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down project plans, specs, or PRDs into disjointed, poorly tracked issues leads to missed dependencies, uneven work distribution, and deliverables that can't be demoed end-to-end. This skill eliminates that friction by enforcing a structured vertical slice decomposition workflow.

Core Features & Use Cases

  • Tracer Bullet Vertical Slicing: Splits work into thin, end-to-end issues that cut through all integration layers (schema, API, UI, tests) instead of isolated single-layer tasks.
  • Dependency & Task Classification: Clearly marks each issue as HITL (requires human input like design review) or AFK (can be implemented autonomously), with explicit blocker relationships to prevent workflow bottlenecks.
  • Standardized Issue Templates: Generates consistent, ready-to-publish issue bodies with clear acceptance criteria, parent references, and blocked-by fields for seamless integration with your team's issue tracker.
  • Use Case: When you have a new feature PRD for a todo app, this skill breaks it into demoable slices like "add user authentication end-to-end (DB schema + API + login UI + tests)" instead of separate, un-runnable tasks for each layer.

Quick Start

Use the to-issues skill to break down the attached product roadmap into independently assignable issues for the engineering team.

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 requirement document into trackable issues?

To break down a PRD into trackable issues, you apply vertical slice decomposition to split specifications into independently assignable work items featuring clear dependencies, standardized templates, and explicit acceptance criteria.

What is tracer bullet vertical slicing in agile development?

Tracer bullet vertical slicing in agile development is a technique that splits work into thin, end-to-end issues cutting through all integration layers like schema, API, UI, and tests, ensuring each work item delivers complete and demoable user value.

How do I map dependencies and classify tasks for issue tracking?

To map dependencies and classify tasks for issue tracking, you mark each work item as either human-in-the-loop requiring manual input or autonomous for independent execution, while defining explicit blocked-by relationships to prevent workflow bottlenecks.

Does vertical slice decomposition work for features needing design review?

Vertical slice decomposition works for features needing design review by classifying those specific issues as human-in-the-loop tasks, ensuring they are explicitly separated from autonomous AFK work items and properly mapped with blocker relationships.

Why use vertical slice issues instead of separate single-layer tasks?

You use vertical slice issues instead of separate single-layer tasks because manual disjointed breakdowns lead to missed dependencies and deliverables that cannot be demoed end-to-end, whereas vertical slices ensure each issue delivers complete user value.