skills.rest
anonymousminati
anonymousminatiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

to-issues

Break plans into dependency-ordered tracer-bullet issues with acceptance criteria.

Updated May 31, 2026
Search Tags:#issue tracking#hitl#prd analysis#vertical slices#tracer bullets#afk#backlog planning
One-click install
npx skills add https://github.com/anonymousminati/Res-POS --skill to-issues-anonymousminati
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: to-issues
Source: https://github.com/anonymousminati/Res-POS/tree/main/.claude/skills/to-issues
Command: npx skills add https://github.com/anonymousminati/Res-POS --skill to-issues-anonymousminati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a plan, spec, or PRD into clear, independently executable issues so teams can move from vague goals to actionable work.

Core Features & Use Cases

  • Tracer-bullet breakdowns: Splits work into thin vertical slices that span schema, API, UI, and tests.
  • Dependency-aware planning: Orders blockers first and labels each slice as HITL or AFK.
  • Issue-ready output: Produces publishable issue bodies with acceptance criteria, blockers, and user-story coverage.
  • Use case: Use it when a product proposal needs to become a prioritized backlog for an issue tracker.

Quick Start

Ask the to-issues skill to break this plan into tracer-bullet issues, then review the proposed slices, dependencies, and HITL or AFK labels.

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 tracer-bullet vertical slices for issue tracking?▼

To break a PRD into tracer-bullet vertical slices, the plan is divided into thin executable issues spanning schema, API, UI, and tests, ensuring each slice delivers end-to-end functionality for issue trackers.

What is the best way to create dependency-aware backlog issues from a spec?▼

Creating dependency-aware backlog issues from a spec involves ordering blockers first and labeling each vertical slice as HITL or AFK, producing publish-ready issue bodies with blocked-by references.

Can I generate publish-ready issue bodies with acceptance criteria from a product roadmap?▼

Yes, you can generate publish-ready issue bodies from a product roadmap by aligning domain glossary terms and mapping user-story coverage, ensuring each issue includes clear acceptance criteria and dependency labels.

How do I label backlog issues as HITL or AFK during PRD analysis?▼

Labeling backlog issues as HITL or AFK during PRD analysis requires evaluating each vertical slice for human-in-the-loop dependencies versus asynchronous execution, then appending the appropriate tag to the issue body.

Does issue tracker context need to be provided for vertical slice planning?▼

Yes, issue tracker context must be provided for vertical slice planning to ensure the generated issues align with the target platform's formatting and dependency tracking requirements.

Why use tracer bullets for breaking down implementation roadmaps instead of horizontal layers?▼

Using tracer bullets for implementation roadmaps creates thin vertical slices that validate architecture end-to-end early, unlike horizontal layers, allowing teams to grab independent, functional issues immediately.

Related Skills

Explore More Product & Management Skills→
assofohdzassofohdz
25

to-prd

Convert conversation context and codebase understanding into structured PRDs and publish them to issue trackers.

Community
Intermediate
hpsgdhpsgd

groom-backlog

Classify backlog items and generate a structured grooming summary.

Official
Intermediate
hgxszhjhgxszhj

to-prd

Generate a production-ready PRD from conversation context and codebase understanding.

Community
Advanced
dgowriedgowrie

prd-to-issues

Convert a PRD into dependency-ordered GitHub issues with vertical slices.

Community
Intermediate