# Tech Review: {ISSUE-KEY}

## Ticket Summary
{summary, type, priority, current estimate if set}

## Codebase Context
{from scout/graph — or [NO_CODEBASE_CONTEXT]}
- Affected files: {list}
- Architecture area: {component/module}
- Related existing code: {patterns, similar implementations}

## Feasibility Assessment
**Rating:** Straightforward | Complex | Needs Spike
**Confidence:** High | Medium | Low

## What
{Scope definition — what exactly needs to change}

## Why
{Business context from ticket + linked issues}

## How
{Implementation approach — high-level, NOT file-level steps}

## Dependencies
- Blocking: {tickets that must complete first}
- Blocked by: {tickets blocking this one}
- External: {APIs, services, third-party}

## Risks
- {risk + severity + mitigation}

## Complexity Signals (for team estimation — NOT an AI estimate)
- Code surface area: {N files, M modules}
- Dependency count: {N blocking, M blocked-by}
- Migration risk: {yes/no}
- Test coverage gap: {existing coverage of affected area}
- Historical: {similar tickets found via JQL}
> These are observations to inform team estimation. The team decides the points.

## Open Questions
- {unresolved items}
