To Issues

---
description: Planı veya PRD'yi dikey dilimler (tracer bullet) olarak issue tracker'a böl.
---

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

## Process

### 1. Gather context

Work from whatever is already in the conversation context. If an issue reference is passed as argument, fetch it from the issue tracker and read its full body and comments.

### 2. Explore the codebase (optional)

If not already done, explore to understand current state. Issue titles and descriptions should use the project's domain glossary vocabulary and respect ADRs.

### 3. Draft vertical slices

Each issue is a thin vertical slice cutting through ALL integration layers end-to-end (schema → API → UI → tests), NOT a horizontal layer slice.

Rules:
- Each slice delivers a narrow but COMPLETE path through every layer
- A completed slice is demoable or verifiable on its own
- Slices are either HITL (requires human) or AFK (agent can complete alone)
- Prefer AFK over HITL where possible

### 4. Quiz the user

Present as a numbered list. For each slice show:
- **Title**: short descriptive name
- **Type**: HITL / AFK
- **Blocked by**: which other slices must complete first
- **User stories covered**: if source has them

Ask: granularity OK? dependencies correct? any to merge/split? HITL/AFK labels correct?

Iterate until approved.

### 5. Publish to issue tracker

Publish in dependency order (blockers first) so you can reference real issue IDs.

<issue-template>
## Parent

Reference to parent issue (if source was an existing issue, otherwise omit).

## What to build

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

Avoid specific file paths or code snippets — they go stale. Exception: prototype snippets that encode a decision more precisely than prose (trim to decision-rich parts only).

## Acceptance criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Blocked by

- Reference to blocking ticket (if any)

Or "None - can start immediately"

</issue-template>