to-issues

name	to-issues
description	Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Source: mattpocock/skills — engineering/to-issues

To Issues

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

3. Draft vertical slices

why-not-mechanizable: skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).

Break the plan into tracer bullet issues. Each issue is a thin vertical slice that cuts through ALL integration layers end-to-end, NOT a horizontal slice of one layer.

Slices may be 'HITL' or 'AFK'. HITL slices require human interaction, such as an architectural decision or a design review. AFK slices can be implemented and merged without human interaction. Prefer AFK over HITL where possible.

- Each slice delivers a narrow but COMPLETE path through every layer (schema, API, UI, tests) `(review-time: see section note)` - A completed slice is demoable or verifiable on its own `(review-time: see section note)` - Prefer many thin slices over few thick ones `(review-time: see section note)`

4. Quiz the user

Present the proposed breakdown as a numbered list. For each slice, show:

• Title: short descriptive name (review-time: see section note)
• Type: HITL / AFK (review-time: see section note)
• Blocked by: which other slices (if any) must complete first (review-time: see section note)
• User stories covered: which user stories this addresses (if the source material has them) (review-time: see section note)

Ask the user:

• Does the granularity feel right? (too coarse / too fine) (review-time: see section note)
• Are the dependency relationships correct? (review-time: see section note)
• Should any slices be merged or split further? (review-time: see section note)
• Are the correct slices marked as HITL and AFK? (review-time: see section note)

Iterate until the user approves the breakdown.

5. Publish the issues to the issue tracker

For each approved slice, publish a new issue to the issue tracker. Use the issue body template below. These issues are considered ready for AFK agents, so publish them with the correct triage label unless instructed otherwise.

Publish issues in dependency order (blockers first) so you can reference real issue identifiers in the "Blocked by" field.

## Parent

A reference to the parent issue on the issue tracker (if the source was an existing issue, otherwise omit this section).

What to build

A concise description of this vertical slice. Describe the end-to-end behavior, not layer-by-layer implementation.

Avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it here and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Acceptance criteria

• Criterion 1 (review-time: see section note)
• Criterion 2 (review-time: see section note)
• Criterion 3 (review-time: see section note)

Blocked by

• A reference to the blocking ticket (if any) (review-time: see section note)

Or "None - can start immediately" if no blockers.

Do NOT close or modify any parent issue.