gza-task-addlisted

# Add Gza Task Create a well-scoped gza task with the appropriate type and configuration. ## Process ### Step 1: Understand gza task conventions Read `/workspace/AGENTS.md` to understand: - Task types (task, explore, plan, implement, review) - Task format conventions - When to use each type ### Step 2: Gather task requirements Ask the user what they want to accomplish. Use AskUserQuestion to gather: 1. **What needs to be done?** - The core objective or problem to solve 2. **Task type** - Present options: - `task` (default) - General purpose task - `explore` - Research, investigation, or discovery work - `plan` - Planning and design work that produces a specification - `implement` - Code implementation based on clear requirements - `review` - Code review or quality assessment - `improve` - Address review feedback and/or unresolved task comments on an implementation. Runs from review findings, from unresolved comments, or from both; comments-only improve is supported when no usable review exists (use `uv run gza improve <impl-id>`) 3. **Additional context** (optional): - Should this be tagged to relate it to other tasks? (--tag TAG, repeatable) - Does this depend on another task? (--depends-on ID) - For implement tasks: Should auto-create a review task? (--review) - For chained work: Is this based on a previous task's output? (--based-on ID) ### Step 3: Generate the task prompt Create a clear, specific prompt that: - States the objective