to-issues

Convert project plans and PRDs into structured issue tracker tickets.

1|Updated Aug 1, 2020
One-click install
npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill to-issues-johanneskonings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/JohannesKonings/JohannesKonings.github.io/tree/main/.agents/skills/to-issues
Command: npx skills add https://github.com/JohannesKonings/JohannesKonings.github.io --skill to-issues-johanneskonings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually breaking down project plans, specifications, or product requirement documents (PRDs) into well-scoped, independently assignable issue tracker tickets is time-consuming and often leads to inconsistent, poorly defined work items that are hard to prioritize and implement.

Core Features & Use Cases

  • Vertical Slice Breakdown: Splits work into tracer bullet issues, each delivering a thin, end-to-end slice through all integration layers (schema, API, UI, tests) instead of horizontal layer-specific chunks.
  • HITL/AFK Classification: Labels each slice as either human-in-the-loop (requiring architectural decisions or design reviews) or AFK (implementable and mergeable without human input) to prioritize work appropriately.
  • Project-Aligned Issues: Ensures issue titles, descriptions, and acceptance criteria use the project's domain glossary and respect existing architectural decision records (ADRs) for consistency.
  • Use Case: A product manager with a new feature PRD can use this skill to generate a set of ready-to-publish, properly scoped issues for their engineering team, each with clear acceptance criteria and dependency tracking.

Quick Start

Use the to-issues skill to break down the attached Q4 feature PRD into a set of trackable issues for the engineering team.

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 product requirement document into trackable issues?

To break down a product requirement document into trackable issues, convert the project plans and specifications into structured, independently assignable tickets with clear acceptance criteria and dependency tracking.

What are vertical slices in issue tracking and why use them?

Vertical slices in issue tracking are tracer bullet issues that deliver a thin, end-to-end slice through all integration layers like schema, API, UI, and tests, instead of horizontal layer-specific chunks, ensuring each slice is independently verifiable.

How do I generate agile tickets that align with project domain vocabulary?

Generate agile tickets aligned with project domain vocabulary by ensuring issue titles, descriptions, and acceptance criteria respect existing architectural decision records and use the project's domain glossary for consistency.

Can I classify issue tracker tickets by implementation priority?

You can classify issue tracker tickets by labeling each slice as either human-in-the-loop, requiring architectural decisions or design reviews, or AFK, meaning implementable and mergeable without human input, to prioritize work appropriately.

Does this work breakdown method support dependency tracking?

This work breakdown method supports dependency tracking by generating structured issues that map relationships between tracer bullet vertical slices, ensuring engineering teams understand implementation order and triage labels.