skills.rest
wzser
wzserCOMMUNITY
Explore all skills by this author →
GitHub

to-issues

Decompose project plans and specifications into granular issues for tracking.

9|Updated May 25, 2026
Search Tags:#project planning#issue management#issue tracking#vertical slicing#plan decomposition
One-click install
npx skills add https://github.com/wzser/supermatrix --skill to-issues-wzser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/wzser/supermatrix/tree/main/platform/skill-master/skills/to-issues
Command: npx skills add https://github.com/wzser/supermatrix --skill to-issues-wzser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The to-issues skill breaks down complex plans, specifications, or product requirements documents (PRD) into individual issues suitable for tracking in a project's issue tracker.

Core Features & Use Cases

  • Plan Decomposition: Converts high-level plans into a set of actionable issues.
  • Issue Creation: Automatically generates issues that can be tracked for progress and resolution.
  • Vertical Slicing: Splits work into end-to-end vertical slices that can be implemented independently.
  • User Collaboration: Allows users to review and refine the issue breakdown before creation.

Quick Start

/new to-issues "Break down the new feature release into independent issues following 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 product roadmap into engineering issues for issue tracking?▼

Issue tracking through plan decomposition is the best way to manage complex product requirements documents because it breaks them into granular issues. This approach allows for user collaboration to review and refine the breakdown before creation.

How does vertical slicing work for issue management?▼

Vertical slicing splits project work into end-to-end vertical slices that can be implemented independently. This issue management technique ensures each slice delivers complete functionality, allowing teams to track and resolve issues without horizontal layer dependencies.

Can I convert user stories into tickets for issue tracking?▼

Yes, you can convert user stories into tickets for issue tracking by decomposing specifications into individual issues. This plan decomposition translates user stories into granular, trackable issues suitable for a project's issue tracker.

Do I need an existing issue tracker to use plan decomposition?▼

Before using this issue management approach, you need knowledge of the project's issue tracker and a methodical approach to vertical slicing. This prerequisite understanding ensures the plan decomposition yields actionable, independently implementable issues.

What is the best way to translate a product requirements document into actionable issues?▼

Issue tracking through plan decomposition is the best way to manage complex product requirements documents because it breaks them into granular issues. This approach allows for user collaboration to review and refine the breakdown before creation.

Related Skills

Explore More Software Engineering Skills→
ckyeonckyeon

to-issues

Break down project plans into manageable issues for issue tracking systems.

Community
Intermediate
huangzidahuangzida
2

to-issues

Convert project plans, specs, or PRDs into actionable issue tickets.

Community
Advanced
Luis-ERPLuis-ERP

integration-slice-orchestration

Orchestrate FE/BE feature integration through incremental vertical slices with frozen contracts.

Community
Advanced
laozhong86laozhong86
1

gxpm-planning

Break plans into traceable vertical slices with dependencies and acceptance criteria.

Community
Intermediate