To tickets

Break an approved plan, specification, or conversation into tracer-bullet vertical slices. Work from the existing conversation and read any referenced spec or issue fully. Inspect the codebase when its current state affects ticket boundaries. Use the project's glossary vocabulary and respect relevant ADRs.

Vertical slicing

• Each ticket must cut a narrow but complete path through every relevant layer—schema, API, UI, and tests—not a horizontal layer-only task.
• Every slice must be independently demoable or verifiable and small enough for one focused implementation session.
• Identify useful prefactoring first when it makes the feature easier to implement, then create a separate prefactoring ticket if needed.
• Avoid broad refactors as vertical slices. For a mechanical change with a wide blast radius, use expand → migrate in batches → contract. Each migration batch is blocked by expand; contract is blocked by every migration batch.
• If migration batches cannot stay green independently, identify the integration dependency and make the final integrate-and-verify ticket explicit.

Blocking edges

Every ticket must declare its blockers:

Blocked by: T01 — Add persisted project record