plan-tasklisted

# Plan Task Produce the smallest plan that lets a capable implementer begin without rediscovering material context or inventing decisions. ## Respect the Planning Contract For a plan-only request, work read-only and do not implement. For an implementation request, plan only enough to coordinate dependent work, then continue without ceremonial approval unless a material decision requires the user. Do not save a plan artifact unless the user requests it or the repository has an authorized convention. Do not convert the plan into tickets unless the user requests independently scheduled work units. ## Choose the Plan Level Use exactly one level: 1. **No formal plan:** the work is obvious, local, low-risk, and verifiable in one or two actions. 2. **Working plan:** three to seven outcome-oriented steps for a bounded task. Track it in the available plan tool when coordination benefits from visible state. 3. **Execution plan:** durable, self-contained milestones for multi-hour, multi-session, risky, or cross-system work. Use only when requested or required by repository convention. Read `references/plan-levels.md` before creating an execution plan. Do not impose its ceremony on ordinary work. When tracking a working plan, keep exactly one step `in_progress`. Mark a completed step immediately after its evidence is available and before starting the next step. Split or revise a step as soon as reality invalidates it; never batch stale status updates at the end. ## Establish Ou