# Refinement: <short ticket title>

## Ticket (summary)

**Number** <Ticket number e.g. SQGZ-430>

**Issue:** <description of the current problem or gap>

**Expected behavior:**
- <point 1>
- <point 2>
- …

---

## Technical context

| Area | Detail |
|------|--------|
| **Module** | <e.g. EmployeeLifecycle, ServiceManagement> |
| **Flow** | <screen or flow where the issue occurs> |
| **Components** | <affected components or forms> |
| **Affected block** | <files, hooks, or specific UI elements> |
| **Data source** | <APIs, queries, state if applicable> |
| **Analog** | <existing file(s) to read before implementing — same pattern, same role> |

**Root cause:** <why the issue occurs or what's missing; one or two sentences>

**Key design decisions:** <non-obvious decisions that constrain the implementation — e.g. "same endpoint handles all types, no new service needed", "reuse X hook without modification". Leave blank if none.>

---

## Components / libraries

<Which UI or design-system components to use. Table or list with component and usage if applicable. Include specific props or keys if helpful.>

---

## Implementation plan

> Each step is a **vertical slice**: by the end of it, something new is visible and testable in the app. Do not start the next step until the current one is confirmed.

### 1. <Step 1 name>

- **Objective:** <what this resolves>
- **Proposal:** <what to do, in which file or folder>
- **Suggested location:** <path>
- **Analog:** <existing file to read before implementing this step, if applicable>
- **✔ How to verify:** <what the user can do in the app to confirm this step works>

### 2. <Step 2 name>

- …
- **✔ How to verify:** …

### N. <Next steps>

- …
- **✔ How to verify:** …

---

## Refinement checklist

- [ ] <question or decision to close with the team>
- [ ] …

---

## Acceptance criteria (for Jira)

1. <criterion 1>
2. <criterion 2>
3. …