to-issues

Convert plans, specs, or PRDs into vertical-slice issues with needs-triage labels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert a plan, spec, or PRD into a set of implementation-ready issues that can be independently grabbed and shipped, instead of leaving work as vague, hard-to-execute prose.

Core Features & Use Cases

  • Tracer-bullet vertical slices: breaks work into thin slices that cut end-to-end across all integration layers.
  • HITL vs AFK planning: marks which slices require human decisions (HITL) versus which can be implemented and merged (AFK).
  • Issue tracker publishing: drafts and publishes each slice as a new issue with acceptance criteria and dependency ordering, applying the needs-triage label.

Example: You have a PRD for a new onboarding flow and need concrete engineering tickets—this skill proposes and publishes vertical-slice issues (with blocked-by dependencies) so teams can start implementing immediately.

Quick Start

Ask the assistant to break your PRD into tracer-bullet vertical slice issues and publish them to the project issue tracker with the correct acceptance criteria and dependencies.

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 vertical slice issues for engineering planning?

To break a PRD into vertical slice issues, you provide the spec to the assistant, which decomposes the work into thin, end-to-end tracer-bullet slices. It then drafts and publishes these slices to your issue tracker with dependency ordering and acceptance criteria.

What is the difference between HITL and AFK classification in issue decomposition?

HITL (Human-in-the-Loop) and AFK (Away-from-Keyboard) classification in issue decomposition marks which vertical slices require human decisions before proceeding and which can be implemented and merged autonomously without manual intervention.

How do I convert project specs into demoable end-to-end slices with dependency mapping?

Converting project specs into demoable end-to-end slices involves analyzing the requirements and drafting issues that cut across all integration layers. Dependency mapping is applied to establish blocked-by relationships, ensuring slices are grabbed in the correct execution order.

Can I publish issues with needs-triage labeling directly from a project plan?

Yes, you can publish issues with needs-triage labeling directly from a project plan. The breakdown process presents the drafted slices for user approval before publishing them to the issue tracker using a standard template with the required triage labels.

Does issue decomposition work for project triage workflows with existing tracker context?

Yes, issue decomposition works for project triage workflows by fetching and summarizing relevant existing issue context when provided. This ensures newly generated vertical-slice issues align with current tracker dependencies and ongoing engineering planning.

When should I not use vertical slices for issue breakdown?

You should not use vertical slices for issue breakdown if your engineering planning requires isolated component-level tasks rather than end-to-end functionality. This approach targets teams needing independently demoable or verifiable slices that cut across all integration layers.