to-issues

Convert project plans and PRDs into structured issue tracker tickets.

4|2|Updated Jun 20, 2026
One-click install
npx skills add https://github.com/saitarrun/devforge-ai --skill to-issues-saitarrun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/saitarrun/devforge-ai/tree/main/skills/plan-breakdown
Command: npx skills add https://github.com/saitarrun/devforge-ai --skill to-issues-saitarrun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down project plans, specs, or PRDs into disjointed, poorly tracked issues leads to messy implementation, unclear dependencies, and wasted engineering time on work that doesn't deliver end-to-end value.

Core Features & Use Cases

  • Vertical Slice Breakdown: Splits work into thin tracer bullet slices that cut through all integration layers (schema, API, UI, tests) for demoable, verifiable increments.
  • HITL/AFK Classification: Labels each slice as human-in-the-loop (requires review/approval) or AFK (can be implemented autonomously) to prioritize work and reduce bottlenecks.
  • Use Case: For a new OAuth login feature PRD, this skill generates issues like "Add OAuth user schema and basic API endpoint" and "Build OAuth callback UI with error handling", each with clear acceptance criteria and dependency tracking.

Quick Start

Use the to-issues skill to break down the attached login feature PRD into trackable vertical-slice 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 convert a PRD into agile tickets for issue tracking?

Vertical slice work decomposition splits features into thin tracer bullet slices that cut through schema, API, UI, and tests, ensuring each issue delivers a demoable, verifiable increment of end-to-end value.

How do I break down project plans into vertical slices for agile development?

Vertical slice work decomposition splits features into thin tracer bullet slices that cut through schema, API, UI, and tests, ensuring each issue delivers a demoable, verifiable increment of end-to-end value.

What is the best way to generate ready-to-publish issues with acceptance criteria from a plan?

The best way to generate ready-to-publish issues is to apply plan breakdown templates that include parent references, end-to-end behavior descriptions, acceptance criteria, and blocker tracking for agile development teams.

Can I classify agile tickets as human-in-the-loop or autonomous during PRD conversion?

Yes, during PRD conversion you can label each vertical slice as either human-in-the-loop, requiring review and approval, or AFK, meaning it can be implemented autonomously, to prioritize work and reduce bottlenecks.

Does this approach to work decomposition track dependencies between tracer bullet slices?

Yes, this work decomposition approach generates structured issues with clear dependency relationships and blocker tracking, ensuring teams understand how each tracer bullet slice relates to others before implementation.