gza-plan-reviewlisted

# Gza Plan Review Run an interactive plan quality gate for a specific plan task before implementation starts. ## Inputs - Required: full prefixed plan task ID (for example, `gza-1234`) If the user did not provide a task ID, ask for it before proceeding. Use the full prefixed task ID for all `gza` commands. ## Process ### Step 1: Inspect the task with built-in gza commands Run these commands with the provided task ID: ```bash uv run gza show <TASK_ID> uv run gza log <TASK_ID> uv run gza history --type plan --limit 10 ``` Use this output to verify: - task exists - task type is `plan` - task status (`completed` is required for a `Go` recommendation) - final plan output and any failure context - nearby plan/review history for dependencies and precedent If the task is not found or is not a `plan` task, stop and return a no-go with corrective actions. ### Step 2: Run the interactive quality gate Use AskUserQuestion to evaluate each gate area. Ask concise, targeted questions and confirm assumptions explicitly. Gate areas: 1. Scope clarity - Is the problem statement specific? - Are boundaries and out-of-scope items explicit? - Are impacted components/files identified? 2. Acceptance criteria - Are there concrete, testable success criteria? - Are behavior, edge cases, and failure modes covered? - Is "done" unambiguous for implementation and review? 3. Risks - Are technical/product risks identified and ranked? - Are mitigation steps or fallback paths defined? - Are unkno