to-issues

Break plans, specs, or PRDs into vertical-slice issues with blocker relationships.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill to-issues-yarma-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/yarma-tech/agent-admin-qonto/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/yarma-tech/agent-admin-qonto --skill to-issues-yarma-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Vertical-slice planning: generate small, end-to-end slices that span from requirements to deployment.
  • HITL / AFK slices: classify slices by whether they require human input or can be automated.
  • Publish to tracker: automatically create issues in your project tracker with proper block relationships and templates.
  • Use Case: convert a product PRD into concrete implementation tickets for developers, QA, and release planning.

Quick Start

Provide a plan, PRD, or issue URL and I will break it into tracer-bullet issues and publish them to your 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 trackable issues for agile development?

Vertical-slice planning decomposes a plan into end-to-end tracer-bullet issues spanning schema, API, UI, and tests. This approach ensures each slice delivers independent functionality across all project layers for continuous integration.

How to create tracer-bullet issues that span all project layers?

To create tracer-bullet issues, provide a plan, PRD, or issue URL to break it into end-to-end slices covering schema, API, UI, and tests. The Skill then publishes these issues directly to your tracker with proper templates and blocker relationships.

Does this issue breakdown tool support classifying slices for automation versus human input?

Yes, the issue breakdown process supports classifying generated slices by HITL and AFK categories. This separates slices requiring human input from those that can be automated, clarifying workflow constraints for developers and release planning.

Can I use this to automatically publish issues with blocker relationships to my tracker?

Yes, you can automatically publish issues to your project tracker with clear blocker relationships to maintain sequencing. The Skill requires the issue-tracker vocabulary and a templated publishing process to establish dependencies between generated slices.

What is the best way to convert a product spec into implementation tickets?

The best way to convert a product spec into implementation tickets is using tracer-bullet vertical slices. This approach generates small, end-to-end issues spanning requirements to deployment, ensuring developers grab independent slices across schema, API, UI, and tests.