gza-explore-summarizelisted

# Gza Explore Summarize Summarize a completed explore task and turn its output into concrete next-step guidance. Use this when an explore task produced useful markdown or notes, but the user wants a faster handoff into planning, implementation, or a narrower follow-up exploration. ## Inputs - Required: full prefixed explore task ID (for example, `gza-1234`) - Optional: context about what decision the user is trying to make next If the user did not provide a full prefixed task ID, ask for it before proceeding. Use the full prefixed task ID for all `gza` commands. ## Goal Produce a concise operator-facing synthesis: - what the explore task found - what matters most - what remains uncertain - what the best next steps are This skill is not a raw inspection dump. Prefer synthesis and recommended actions over repeating the whole report. ## Process ### Step 1: Inspect the task Run: ```bash uv run gza show <TASK_ID> uv run gza log <TASK_ID> ``` Use the output to verify: - task exists - task type is `explore` - current status - report or output content - any execution/log context that changes how confident the findings are If the task is not found or is not an `explore` task, stop and explain the mismatch. ### Step 2: Read the exploration output Use the report content from `gza show` or the report file it references. Extract: - main findings - evidence or examples that support those findings - recommendations already present in the report - unresolved unknowns, risks