Break Feature Into Steps

# Break Feature into Steps

## Recipe

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

## Purpose

Turn an already-defined feature into a sequence of small, ordered, independently verifiable implementation steps for an existing Lovable project. The output should reduce risk, avoid broad rewrites, preserve working behavior, and make each step suitable for a separate implementation prompt.

## Use When

- a feature plan exists but is too large to implement safely in one prompt
- the feature spans UI, backend, database, permissions, integrations, or testing
- a risky change needs staged delivery
- implementation should proceed one milestone at a time
- the team wants clear checkpoints and rollback boundaries
- previous broad prompts caused regressions or unrelated changes

## Do Not Use When

- the feature is not yet defined well enough to plan
- a full project analysis is still required
- the task is a single isolated change
- the primary need is debugging an unknown failure
- unrelated features have been grouped into one request

## Required Context

Provide when known:

- `[FEATURE]`: Feature to decompose
- `[FEATURE_PLAN]`: Existing plan, specification, or accepted behavior
- `[USER_OUTCOME]`: Result the user must achieve
- `[ACCEPTANCE_CRITERIA]`: Observable completion conditions
- `[CURRENT_STATE]`: Relevant behavior that already exists
- `[AFFECTED_AREAS]`: Known routes, components, data, permissions, or integrations
- `[CONSTRAINTS]`: Technical, product, design, security, or compatibility limits
- `[OUT_OF_SCOPE]`: Explicit exclusions
- `[DELIVERY_PREFERENCE]`: Vertical slices, technical layers, or safest order
- `[MAX_STEP_SIZE]`: Maximum scope allowed per implementation step
- `[KNOWN_RISKS]`: Fragile areas, migration concerns, or external dependencies

## Prompt