Plan Feature

# Plan Feature

## Recipe

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

## Purpose

Create a focused, implementation-ready plan for one feature in an existing Lovable project. The plan must be grounded in the current project, preserve established behavior, expose material uncertainties, and divide the work into safe, verifiable steps without changing the project.

## Use When

- adding a new feature to an existing project
- extending an existing flow
- preparing a database, auth, billing, integration, or UI change
- the feature touches multiple files or systems
- the implementation path is not yet agreed
- acceptance criteria need to be clarified before coding

## Do Not Use When

- the requested change is already trivial, isolated, and fully specified
- the primary task is debugging an unknown failure
- a full project analysis is required first
- implementation has already been approved and only execution remains
- the request combines several unrelated features

## Required Context

Provide when known:

- `[FEATURE]`: Feature or capability to plan
- `[USER]`: Primary actor
- `[USER_GOAL]`: Outcome the actor needs
- `[BUSINESS_REASON]`: Why the feature matters
- `[CURRENT_BEHAVIOR]`: What exists now
- `[DESIRED_BEHAVIOR]`: Expected behavior
- `[ENTRY_POINT]`: Route, page, component, or trigger
- `[ACCEPTANCE_CRITERIA]`: Observable success conditions
- `[CONSTRAINTS]`: Product, technical, security, design, time, or compatibility limits
- `[OUT_OF_SCOPE]`: Explicit exclusions
- `[KNOWN_FILES]`: Relevant files or systems, when known
- `[KNOWN_RISKS]`: Existing concerns or fragile areas

## Prompt