/to-issues
RequirementsUser-invoked

Split an approved PRD or plan into vertical-slice GitHub issues so people or agents can grab work without waiting on a giant epic.

When to use

The PRD or plan is approved and you need tracker-ready work items.

Prerequisites

  • /setup done; tracker CLI working.
  • An approved PRD, plan, or story set to slice (issue number or path).

How to use

  1. Invoke /to-issues and point at the PRD or plan (e.g. PRD #42).
  2. Review proposed vertical slices — adjust granularity when quizzed.
  3. Approve publish; issues land with labels such as `ready-for-agent` when configured.
  4. Pick the first unblocked slice and hand off to /dev.

Done when

Independent tracker issues exist for each vertical slice and the first /dev target is clear.

Pipeline

Upstream
/reqs or /to-prd
Downstream
/dev (via agent briefs or direct pickup)

Boundaries

Does not triage raw backlog issues — that is /triage. Needs /setup first.

Tips

  • /to-issues creates slices from a spec; /triage processes inbound backlog.
  • Prefer one vertical slice per issue — avoid giant epics agents cannot finish.

Sample prompt

prompt
/to-issues

PRD #42
← Skill catalog