planlisted

# zuvo:plan Create a detailed, task-by-task implementation plan. Every task follows the TDD protocol: RED (failing test) -> GREEN (minimal code) -> Verify -> Commit. --- ## Input Resolution Determine the planning input. Two modes: **spec-driven** (from brainstorm output) or **inline** (from user description). ### Step 1: Look for a spec 1. If the user provided an explicit path (e.g., `zuvo:plan docs/specs/my-spec.md`), use that file 2. Otherwise, search: `Glob("docs/specs/*-spec.md")` 3. If multiple specs exist, present the list and ask the user which one to plan against ### Step 2: Determine mode - **Spec found with `status: Approved`** → **spec-driven mode**. Read spec in full. This is the source of truth. - **Spec found without `status: Approved`** → Print: "Spec exists but is not approved. Using it as reference in inline mode." Treat spec as context, not authority. → **inline mode**. - **No spec found** → **inline mode**. ### Inline mode requirements The user's message (argument to `zuvo:plan`) IS the planning input. Extract: - **Goal:** what they want built - **Scope:** which files/areas are affected (explore codebase if not stated) - **Constraints:** any stated requirements If the user's description is too vague to plan against (less than one sentence, no clear deliverable), ask ONE clarifying question. Do not block — a couple of sentences is enough to plan from. Set `planning_mode: "inline"` or `planning_mode: "spec-driven"` — this affects the plan document