to-issues

Breaks plans and specs into vertical-slice issues on a project issue tracker.

1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/mst-software-vn/mst-checkscam --skill to-issues-mst-software-vn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/mst-software-vn/mst-checkscam/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/mst-software-vn/mst-checkscam --skill to-issues-mst-software-vn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a large plan, spec, or PRD into actionable work items is hard: teams often create horizontal, layer-by-layer tasks that cannot be demoed or completed independently. This Skill decomposes planning documents into thin vertical slices (tracer bullets) that cut through all layers end-to-end, then publishes them as ready-to-grab issues on the project's issue tracker. ## Core Features & Use Cases - Vertical Slice Decomposition: Splits a plan into tracer-bullet issues where each slice spans schema, API, UI, and tests, so every issue is independently demoable. - Interactive Refinement: Presents the proposed breakdown with titles, dependencies, and covered user stories, then iterates with the user until the granularity and blocking relationships are approved. - Issue Tracker Publishing: Creates issues in dependency order using a structured template (What to build, Acceptance criteria, Blocked by) with the correct triage label for AFK agents. - Use Case: After drafting a PRD for a new feature, run this Skill to convert it into 5-8 ordered issues that team members or autonomous agents can pick up immediately without further planning meetings. ## Quick Start Ask the assistant to break the current plan or spec into independently-grabbable vertical-slice issues and publish them to the issue 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 a PRD into issues for my team?▼

Provide the plan, spec, or PRD in the conversation and invoke the Skill. It drafts tracer-bullet vertical slices, quizzes you on granularity and dependencies, then publishes approved issues to your issue tracker in dependency order.

What is a vertical slice or tracer bullet issue?▼

A vertical slice is a thin piece of work that cuts through all integration layers end-to-end, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is independently demoable or verifiable.

Does this Skill work with my issue tracker?▼

The Skill expects an issue tracker integration and triage label vocabulary to be configured beforehand, via the referenced setup command. Without that setup, it cannot fetch issue references or publish new issues.

Can I adjust the issue breakdown before publishing?▼

Yes. The Skill presents the proposed slices as a numbered list with titles, blockers, and covered user stories, then asks whether granularity and dependencies are correct. It iterates until you approve before publishing anything.

What goes into each published issue?▼

Each issue follows a template with an optional parent reference, a concise end-to-end description of what to build, a checklist of acceptance criteria, and a Blocked by section referencing real issue identifiers published earlier.