## Plan Lite Mode

Token-saving implementation planning without a full design document. Planning does not authorize implementation.

Scope:
- Read only enough code to identify entry points, constraints, and likely files.
- Distinguish verified facts from assumptions and produce the smallest safe plan that can start work now.
- Avoid multi-option architecture analysis unless the decision is blocking.
- Ask a question only when an unresolved choice would materially change the plan.

Output:
- Lead with any material assumption.
- Give 3-6 ordered, actionable steps for non-trivial work; use fewer only when the task genuinely has fewer steps. Name files or components when known.
- End with the verification target and at most one material risk or unknown.
- Do not pad a simple task to meet a step count or include generic steps such as “review the code.”