to-issues

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

2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill to-issues-momodaviluke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/MomoDaviluke/star-citizen-promotion/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/MomoDaviluke/star-citizen-promotion --skill to-issues-momodaviluke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Core Features & Use Cases

  • Break high-level plans into end-to-end, independently deliverable issues.
  • Enforce consistent vocabulary and triage labeling across issues.
  • Provide a repeatable workflow from context gathering to issue publishing.

Quick Start

Break down the current plan or PRD into tracer-bullet issues in the project tracker.

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 PRD into independently deliverable issues?

Tracer-bullet vertical slices divide a project plan into end-to-end, independently grabbable issues. This methodology ensures each ticket delivers a thin working slice of functionality across all necessary layers.

How do I create consistent issue breakdowns across multiple teams?

To create consistent issue breakdowns across teams, the Skill enforces consistent vocabulary and triage labeling. It provides a repeatable workflow from context gathering to publishing executable tickets on the issue tracker.

What is the best way to convert a project spec into tracker tickets?

To create consistent issue breakdowns across teams, the Skill enforces consistent vocabulary and triage labeling. It provides a repeatable workflow from context gathering to publishing executable tickets on the issue tracker.

Can I use tracer-bullet methodology for project issue breakdowns?

To create consistent issue breakdowns across teams, the Skill enforces consistent vocabulary and triage labeling. It provides a repeatable workflow from context gathering to publishing executable tickets on the issue tracker.

Does this issue breakdown approach work without external dependencies?

To create consistent issue breakdowns across teams, the Skill enforces consistent vocabulary and triage labeling. It provides a repeatable workflow from context gathering to publishing executable tickets on the issue tracker.