to-issues

Convert plans, specs, or PRDs into tracker issues with vertical slices.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/SamyakJhaveri/loam --skill to-issues-samyakjhaveri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/SamyakJhaveri/loam/tree/main/cultivation/marketplace/pocock-engineering/skills/to-issues
Command: npx skills add https://github.com/SamyakJhaveri/loam --skill to-issues-samyakjhaveri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Break plans into vertical slices that cover end-to-end work across all layers.
  • Generate implementable issues with clear scope and acceptance criteria.
  • Use when converting a plan, spec, or PRD into actionable tasks for a team.

Quick Start

Describe a plan as tracer-bullet vertical slices and publish each slice as an issue on the 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 trackable issues for project management?

To break down a PRD into trackable issues, you convert the plan into tracer-bullet vertical slices that cover end-to-end work across all layers, then publish each slice as an independently-grabbable issue on the tracker.

What are tracer-bullet vertical slices in issue tracking?

Tracer-bullet vertical slices are end-to-end work segments spanning all project layers used to break down plans. They generate implementable issues with clear scope, acceptance criteria, and defined blockers to maintain traceability across teams.

Can I use this workflow to convert a spec into actionable tasks for multiple teams?

Yes, you can convert a spec into actionable tasks for multiple teams. The workflow breaks down work into vertical slices and generates issues with clear scope, ensuring tasks are independently-grabbable and trackable across teams.

What is the best way to structure implementation tickets from a project plan?

The best way to structure implementation tickets from a project plan is to enforce a structured breakdown using vertical slices. This defines issue schemas, scope, acceptance criteria, and blockers to maintain traceability on the project tracker.

Does breaking down work into vertical slices help with triage on an issue tracker?

Breaking down work into vertical slices helps with triage by creating independently-grabbable issues on the project tracker. Each issue features clear scope and acceptance criteria, making it easier to assign and track work across teams.