skills.rest
ZzAve
ZzAveCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Convert plans into verified issues with vertical slices in an issue tracker.

Updated Mar 17, 2026
Search Tags:#project management#issue tracker#issue creation#tracer bullets#plan breakdown
One-click install
npx skills add https://github.com/ZzAve/teambalance-app --skill to-issues-zzave
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/ZzAve/teambalance-app/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/ZzAve/teambalance-app --skill to-issues-zzave

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of breaking down plans, specifications, or PRDs into independently manageable issues on the project issue tracker, streamlining the workflow and improving efficiency.

Core Features & Use Cases

  • Plan to Issues Conversion: Transform high-level plans or requirements into actionable issues.
  • Vertical Slices Creation: Generate vertical slices (tracer bullets) for each issue, ensuring comprehensive coverage.
  • User Verification: Present the proposed issue breakdown for user verification and adjustment.
  • Issue Tracker Integration: Publish the issues to the issue tracker with appropriate labels and dependency information.

Quick Start

Use the to-issues skill to create issues from the plan 'project-plan.md'.

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 project plan into issues in an issue tracker?▼

Convert a project plan into issues by using automated plan breakdown to transform high-level requirements into actionable issues, applying vertical slicing to cover all layers, and publishing them directly to the issue tracker.

What are vertical slices in issue creation and why are they used?▼

Vertical slices, or tracer bullets, in issue creation are generated to ensure comprehensive coverage across all layers of a plan. They create independently manageable issues that span the full technical stack for each feature.

Can I review and adjust issues before they are published to the issue tracker?▼

You can review and adjust issues before publication because the breakdown process presents the proposed issues for explicit user verification, ensuring you approve the tracer bullets and dependencies before they are published.

Do I need an issue tracker integration to break down plans into issues?▼

An issue tracker integration is required to break down plans into issues, as the Skill needs to publish the verified issues with appropriate labels and dependency information directly to the project issue tracker.

What is the best way to break down a PRD into manageable issues?▼

The best way to break down a PRD into manageable issues is to automate the conversion of specifications into vertical slices, verify the proposed breakdown, and publish the actionable issues with dependency information to the tracker.

Are there limitations when automating issue breakdown from high-level plans?▼

A limitation of automating issue breakdown is that it requires user verification before publishing, meaning it cannot autonomously publish issues to the tracker without explicit user approval of the proposed slices and dependencies.

Related Skills

Explore More Software Engineering Skills→
cagdotincagdotin
36

to-issues

Break down plans, specs, or PRDs into tracer-bullet issues for project trackers.

Community
Intermediate
MomoDavilukeMomoDaviluke
2

to-issues

Convert plans, specs, or PRDs into tracer-bullet issues on the project tracker.

Community
Intermediate
sebc-devsebc-dev

to-issues

Convert project plans and specifications into individual issues for issue trackers.

Community
Intermediate
AtharvaN16AtharvaN16

to-issues

Convert project plans into labeled, dependency-managed issues via vertical slicing.

Community
Advanced