gza-plan-improvelisted

# Gza Plan Improve Refine a draft plan through a deliberate question loop. Use this when the user has a rough plan, an incomplete completed plan task, or a draft that needs sharper scope, acceptance criteria, sequencing, risks, and test strategy before implementation begins. ## Inputs Accept one of these inputs: - Preferred: a full prefixed plan task ID (for example, `gza-1234`) - Also supported: pasted draft plan text - Optional: extra constraints, related task IDs, or notes about what feels weak If the user provides neither a full prefixed plan task ID nor draft plan text, ask for the current draft or plan task first. Use the full prefixed task ID for all `gza` commands. ## Goal Produce an improved plan, not just a score. The skill should: - identify the highest-leverage gaps in the current draft - ask concise questions to close those gaps - confirm assumptions explicitly instead of guessing - rewrite the plan into a cleaner, more implementation-ready shape - call out any remaining blockers or open questions This is different from `/gza-plan-review`: - `/gza-plan-review` decides `Go` / `No-go` - `/gza-plan-improve` actively helps the user strengthen the plan first ## Process ### Step 1: Gather the current plan and context If the input is a full prefixed plan task ID, inspect it with: ```bash uv run gza show <TASK_ID> uv run gza log <TASK_ID> ``` Use that output to extract: - task type and status - original prompt - current plan/report content - nearby context