Assess Change Impact

# Assess Change Impact

## Recipe

- Category: Planning
- Recommended mode: Plan Mode
- Risk level: Medium to High
- Estimated scope: Small to Large

## Purpose

Assess the likely impact of a proposed change before implementation. The analysis should identify affected users, flows, files, data, permissions, integrations, tests, deployment behavior, and operational risks without modifying the project.

## Use When

- changing an existing feature or flow
- modifying shared components, schemas, APIs, auth, RLS, billing, storage, or integrations
- preparing a refactor, migration, provider change, or deprecation
- the change may affect multiple routes, roles, tenants, or environments
- rollback or compatibility risk is unclear
- the team needs a go/no-go recommendation before implementation

## Do Not Use When

- the task is a new feature with no existing behavior to preserve
- a complete project analysis is still required
- the change is already implemented and needs regression testing
- the primary task is diagnosing an unknown bug
- the requested work is trivial, isolated, and fully understood

## Required Context

Provide when known:

- `[PROPOSED_CHANGE]`: What may be changed
- `[REASON]`: Why the change is being considered
- `[CURRENT_BEHAVIOR]`: Existing behavior or contract
- `[DESIRED_BEHAVIOR]`: Intended result
- `[KNOWN_SCOPE]`: Routes, files, features, data, or integrations believed to be affected
- `[USERS_OR_ROLES]`: Actors who may be affected
- `[CONSTRAINTS]`: Product, technical, security, design, legal, or operational limits
- `[OUT_OF_SCOPE]`: Explicit exclusions
- `[ROLLBACK_EXPECTATION]`: Required reversibility or recovery behavior
- `[DEPLOYMENT_CONTEXT]`: Prototype, MVP, production, staged rollout, or other
- `[KNOWN_RISKS]`: Existing concerns or fragile areas

## Prompt