to-issues

Convert unstructured project plans into ordered issue tracker tickets with dependencies.

25|5|Updated Apr 22, 2017
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill to-issues-assofohdz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill to-issues-assofohdz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually converting project plans, specs, and PRDs into issue tracker tickets leads to disjointed work, missed dependencies, and unverifiable tasks that are hard to assign and track.

Core Features & Use Cases

  • Tracer Bullet Vertical Slice Breakdown: Splits work into thin, end-to-end slices that cut through all integration layers, so each issue delivers a complete, demoable piece of functionality.
  • Automatic Dependency Tracking: Clearly identifies which issues must be completed before others can start, eliminating blockers and confusion.
  • HITL/AFK Classification: Separates tasks requiring human input (like architectural decisions) from automatable tasks to streamline workflow.
  • Use Case: For example, if you have a PRD for a new multiplayer game mode for Subspace Infinity, this skill breaks it into ordered, independently assignable issues that each deliver a testable piece of the feature.

Quick Start

Use the to-issues skill to break down the Subspace Infinity cross-platform client roadmap into trackable vertical slice issues for your 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 unstructured product requirement documents into trackable issue tickets?

To convert product requirement documents into trackable issue tickets, you can use a work breakdown process that transforms unstructured plans into structured, independently assignable issues with explicit dependency relationships and standardized acceptance criteria.

What is a vertical slice in agile work breakdown and why use it for issue tracking?

A vertical slice in agile work breakdown is a thin, end-to-end piece of functionality that cuts through all integration layers. Using it for issue tracking ensures each ticket delivers a complete, demoable, and verifiable result.

Can I split a game development roadmap into ordered, demoable issues?

Yes, you can split a game development roadmap into ordered, demoable issues by applying tracer bullet vertical slice breakdown, which produces testable issues tailored for software and game development workflows.

How do you classify issue tracker tickets for human input versus automatable tasks?

You classify issue tracker tickets for human input versus automatable tasks using HITL/AFK classification, separating architectural decisions requiring human input from automatable tasks to streamline workflow.

Does this work breakdown approach handle dependency tracking for project planning?

Yes, this work breakdown approach handles dependency tracking for project planning by clearly identifying which issues must be completed before others can start, thereby eliminating blockers and confusion.