To Issues

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

Process

1. Gather context

Work from whatever is already in the conversation context.

2. Explore the codebase (optional)

If you have not already explored the codebase, do so to understand the current state of the code.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."

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.

• 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
• Any prefactoring should be done first

4. Quiz the user

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

• Title: short descriptive name
• Blocked by: which other slices (if any) must complete first
• User stories covered: which user stories this addresses

Ask the user:

• Does the granularity feel right?
• Are the dependency relationships correct?
• Should any slices be merged or split further?

5. Publish the issues to the issue tracker

For each approved slice, publish a new issue to the issue tracker. Publish issues in dependency order (blockers first).

Issue template:

## Parent

A reference to the parent issue on the issue tracker.

## What to build

A concise description of this vertical slice. Describe the end-to-end behavior.

## Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2

## Blocked by

- A reference to the blocking ticket (if any)

Do NOT close or modify any parent issue.