to-issues

Break plans, specs, and PRDs into actionable issue tracker tickets.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/babually/bongo-template --skill to-issues-babually
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/babually/bongo-template/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/babually/bongo-template --skill to-issues-babually

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps break a plan, spec, or PRD into clear, independently actionable issue tracker tickets so teams can move from idea to execution without losing scope or dependencies.

Core Features & Use Cases

  • Vertical Slice Planning: Converts broad work into thin end-to-end issues that each cover a complete tracer bullet through schema, API, UI, and tests where relevant.
  • Dependency Mapping: Identifies blockers and orders issues so implementation can start with the right foundation.
  • Issue Publishing Workflow: Prepares issue-ready descriptions with acceptance criteria, blockers, and user-story coverage for a project tracker.
  • Use Case: A product manager pastes a PRD and gets a structured breakdown of implementation tickets that an engineering team can review and publish.

Quick Start

Ask the assistant to break your plan, spec, or PRD into vertical-slice issues for your project 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 actionable issue tracker tickets?

To break a PRD into actionable issue tracker tickets, you can use a project management workflow that decomposes specifications into independently actionable issues. This process structures work into vertical slices, each containing an issue title, blocker, and acceptance criteria aligned to project tracker triage conventions.

What is tracer bullet planning in project management?

Tracer bullet planning in project management converts broad work into thin, end-to-end vertical slices. Each issue covers a complete tracer bullet through schema, API, UI, and tests where relevant, ensuring implementation starts with the right foundation and maintains dependency ordering.

How do I map dependencies when creating implementation tickets from a spec?

Mapping dependencies when creating implementation tickets involves identifying blockers and ordering issues so implementation can start with the right foundation. This ensures each issue draft includes dependency ordering and acceptance criteria for reviewable project tracker integration.

Can I use this to prepare issue-ready descriptions with acceptance criteria for an engineering team?

Yes, you can prepare issue-ready descriptions with acceptance criteria, blockers, and user-story coverage for an engineering team. This issue publishing workflow generates reviewable issue drafts that align with project tracker triage conventions for product delivery.

What is the best way to structure issues for vertical slice delivery?

The best way to structure issues for vertical slice delivery is to break plans into thin end-to-end issues that each cover a complete tracer bullet. This requires an issue title, blocker, and acceptance-criteria structure aligned to project tracker triage conventions for reviewable drafts.