to-issues

Convert plans, specs, or PRDs into tracer-bullet vertical slice issues.

Updated May 15, 2026
One-click install
npx skills add https://github.com/az9713/engineer-skills-tutorial --skill to-issues-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/az9713/engineer-skills-tutorial/tree/main/skills/engineering/to-issues
Command: npx skills add https://github.com/az9713/engineer-skills-tutorial --skill to-issues-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a plan, spec, or PRD into a set of independently-grabbable issues on your project tracker using tracer-bullet vertical slices, enabling end-to-end traceability from concept to delivery.

Core Features & Use Cases

  • Vertical slices: Breaks work into thin, end-to-end tickets that cover all integration layers.
  • HITL/AFK routing: Classifies slices as requiring human oversight or automation, with clear blockers.
  • Publish-ready issues: Produces a ready-to-create set of issues and their metadata for your tracker.

Quick Start

Provide your plan, PRD, or issue reference and run the skill to generate a ready-to-publish set of tracer-bullet issues.

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 actionable issues for an agile sprint?

To break a PRD into actionable issues, this Skill converts your plan into independently-grabbable tickets using tracer-bullet vertical slices. It generates ready-to-publish issues annotated with type, dependencies, and acceptance criteria for agile sprints.

What are tracer-bullet vertical slices in project planning?

Tracer-bullet vertical slices are thin, end-to-end tickets that cover all integration layers. This approach breaks work into independently-grabbable issues, ensuring complete traceability from high-level goals to concrete tracker tickets.

How do I classify issue tickets as HITL or AFK during triage?

To classify issue tickets during triage, this Skill annotates each generated issue as either HITL, requiring human oversight, or AFK, suitable for automation. This routing clarifies blockers and automation potential for your project tracker.

Does this approach work for converting engineering handoff specs into tracker issues?

Yes, this approach works for engineering handoffs. It takes a spec or plan and coordinates context gathering, slice generation, and per-issue annotations to produce a publish-ready set of tracker issues with clear dependencies.

Can I generate issues with acceptance criteria and dependencies from a high-level plan?

Yes, you can generate issues with acceptance criteria and dependencies from a high-level plan. The Skill processes your plan or spec to produce ready-to-create issues with complete metadata, including type, dependencies, and acceptance criteria.

What is the best way to ensure end-to-end coverage when creating project issues?

The best way to ensure end-to-end coverage is using tracer-bullet vertical slices. This Skill breaks your plan into thin, independently-grabbable tickets that span all integration layers, ensuring full traceability from concept to delivery.