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.
disable-model-invocation	true

To Issues

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

Issue tracker: Local Markdown

Issues live as markdown files under .scratch/

Conventions

• One feature per directory: .scratch/<feature-slug>/
• The PRD is .scratch/<feature-slug>/PRD.md
• Implementation issues are .scratch/<feature-slug>/issues/<NN>-<slug>.md, numbered from 01
• Triage state is recorded as a Status: line near the top of each issue file
• Comments and conversation history append to the bottom of the file under a ## Comments heading

When this skill says "publish to the issue tracker"

Create a new file under .scratch/<feature-slug>/issues/, creating directories as needed.

When this skill says "fetch the relevant ticket"

Read the file at the referenced path. The user will normally pass the path or the issue number directly.

Triage Labels

The skill speaks in terms of five canonical triage roles. This table maps those roles to status strings used in local markdown issue files.

Label in mattpocock/skills	Status in local tracker	Meaning
needs-triage	needs-triage	Maintainer needs to evaluate this issue
needs-info	needs-info	Waiting on reporter for more information
ready-for-agent	ready-for-agent	Fully specified, ready for an AFK agent
ready-for-human	ready-for-human	Requires human implementation
wontfix	wontfix	Will not be actioned

When this skill mentions a role, use the corresponding status string from this table.

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

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) - A completed slice is demoable or verifiable on its own - Prefer many thin slices over few thick ones

4. Quiz the user

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

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

Ask the user:

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

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 status unless instructed otherwise.

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

Status: ready-for-agent

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
• Criterion 2
• Criterion 3

Blocked by

• A reference to the blocking ticket (if any)

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

Comments

Do NOT close or modify any parent issue.