to-issues

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

To Issues

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

Use the local tracker, triage metadata, and domain docs in skills/productivity/setup-skills/. Run /setup-skills if those docs are missing or stale.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes an issue path as an argument, read the local markdown file and its comments. If the user passes a bare issue number, look for the matching numbered file under .scratch/**/issues/.

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 local tracker

For each approved slice, publish a new issue to .scratch/<feature-slug>/issues/<NN>-<slug>.md. Use the issue body template below. Publish AFK slices with Status: ready-for-agent and HITL slices with Status: ready-for-human unless instructed otherwise.

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

Category: bug / enhancement Status: ready-for-agent / ready-for-human

Parent

A relative markdown path to the parent PRD or issue (if the source was an existing tracker file, 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 relative markdown path to the blocking issue (if any)

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

Do NOT close or modify any parent issue.