to-issues

Break plans and PRDs into vertical-slice issues on a project issue tracker.

Updated Sep 20, 2024
One-click install
npx skills add https://github.com/AnasIsmai1/dotfiles --skill to-issues-anasismai1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/AnasIsmai1/dotfiles/tree/main/agents/.agents/skills/to-issues
Command: npx skills add https://github.com/AnasIsmai1/dotfiles --skill to-issues-anasismai1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a large plan, spec, or PRD into actionable work items is hard: horizontal slices create blocked, non-demoable tasks, and ad-hoc breakdowns produce inconsistent issues. This Skill decomposes plans into tracer-bullet vertical slices and publishes them as ready-to-grab issues on the project issue tracker. ## Core Features & Use Cases - Vertical Slice Breakdown: Splits work into thin end-to-end slices that cut through all layers (schema, API, UI, tests) so each issue is independently demoable. - Interactive Refinement: Presents the proposed breakdown with titles, dependencies, and user stories, then iterates with the user until the granularity is approved. - Structured Issue Publishing: Publishes issues in dependency order using a consistent template with acceptance criteria and blocker references, tagged with the correct triage label. - Use Case: After drafting a PRD for a new feature, run this Skill to convert it into a sequence of dependency-ordered tracker issues that AFK agents or teammates can pick up immediately. ## Quick Start Ask the assistant to break the current plan or PRD into independently-grabbable 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 the Skill drafts tracer-bullet vertical slices, each cutting through all layers end-to-end. After you approve the breakdown, it publishes the issues to your issue tracker in dependency order.

What is a vertical slice or tracer bullet issue?▼

A vertical slice is a thin but complete path through every layer of the system, such as schema, API, UI, and tests, rather than a horizontal slice of one layer. Each completed slice is independently demoable or verifiable.

Can I convert an existing tracker issue into sub-issues?▼

Yes. Pass an issue number, URL, or path as an argument and the Skill fetches the full body and comments, then derives slices from it. Published sub-issues reference the parent issue, which is left unmodified.

Does the issue breakdown require codebase exploration?▼

Codebase exploration is optional but recommended. It ensures issue titles use the project's domain glossary, respect relevant ADRs, and identify prefactoring opportunities before implementation begins.

What happens if the issue tracker or triage labels are not configured?▼

The Skill expects the issue tracker and triage label vocabulary to have been provided beforehand. If they are missing, it instructs you to run the setup command for the skill collection first.