gza-task-draftlisted

# Draft Gza Task Guide the user through a deliberate task creation process: clarify scope, surface risks, draft a prompt, get approval, then run `uv run gza add`. ## Step 1: Read conventions Read `/workspace/AGENTS.md` — specifically the "Creating Tasks from Conversations" section — to understand task types, flags, and prompt conventions. ## Step 2: Assess description detail Evaluate how detailed the user's description already is: **If vague or missing key context** (objective unclear, scope undefined, approach unspecified): ask clarifying questions using AskUserQuestion (max 4 questions per call, 2–4 options each). Focus on what matters most: - What is the core objective / what problem does this solve? - What type of work is this? (explore/plan/implement/review/task) - Are there constraints, dependencies, or related tasks? - What does "done" look like? **If already detailed** (clear objective, known scope, specific requirements): skip to Step 3 directly. ## Step 3: Draft the prompt + surface concerns Draft a task prompt that: - States the objective clearly and specifically - References file paths, modules, or components when known - Sets scope (what's in and out) - Includes acceptance criteria for implement tasks - Includes non-goals for implement tasks so the agent does not expand scope silently - Names required tests or concrete failure modes to cover when known - Calls out docs/help/config updates when operator-facing behavior changes - Is appropriately sized (o