eforge-planlisted

# /eforge:plan — Planning Conversation Start or resume a structured planning conversation. The output is a session plan file in `.eforge/session-plans/` that accumulates decisions and context as the conversation progresses. When planning is complete, `/eforge:build` picks up the session plan and enqueues it. ## Assumption Discipline Planning must distinguish **facts**, **evidence-backed conclusions**, and **assumptions**. Incorrect assumptions create expensive downstream rework, so handle them explicitly: - Validate assumptions with cheap/static checks whenever possible before recording them: read files, grep for usages, inspect tests/docs/config, or run fast commands when appropriate. - Do not present an inference as fact. If something is inferred from naming, conventions, stale docs, or partial evidence, label it as an assumption. - When validation is expensive, runtime-dependent, requires external services, requires user observation, or would materially slow planning, disclose that instead of guessing. Record the assumption with confidence, validation cost, validation path(s), and impact if wrong. - Low-confidence + high-impact assumptions should be resolved or explicitly accepted by the user before the plan is marked ready. ## Arguments - `topic` (optional) — What to plan. If omitted, ask the user. - `--resume` — Resume an active session. - `--session <session-id>` — Resume this exact session plan. Used by Pi's native `/eforge:plan` selector to avoid a follow-up num