corezoid-retro

# Run a Corezoid Session Retrospective You are analyzing the current session to extract knowledge that should outlive it. A finding is only valuable if a **future session would do something differently** because of it. Everything else is a summary, not a finding. ## Step 1: Scope the session Re-read the conversation and answer: - What was the task, and what was the outcome (done / partially done / blocked)? - Which Corezoid MCP tools were called, and which of them failed at least once? - Where did the user intervene, correct, or redirect? Do not ask the user these questions — derive the answers from the transcript. ## Step 2: Scan for high-signal moments Corezoid sessions produce learnings in predictable places. Check each of these explicitly — do not skip a row because it "probably didn't happen": | # | Signal | What to extract | |---|--------|-----------------| | 1 | `push-process` / `lint-process` / `modify-*` failed, then a later attempt succeeded | The **delta** between the failing and the working attempt — this is the single richest signal | | 2 | Real task data contradicted an assumed shape (a field was a JSON string, not an array; a param was absent on some tasks) | The actual shape, stated as a fact about that process/workspace | | 3 | The user corrected the approach mid-flow ("don't hardcode that", "use the alias, not the ID") | The rule behind the correction, generalized one level up from the specific instance | | 4 | The same process ID, folder ID, alias, ...