kami
0af2f200d8
Live incident: "Write a web-ui for Correx" resolved to a pre-existing parent epic (webui-8, with children webui-9..14). The old prompt only said "name a task that covers this work" and, separately, "after decomposing, name the single ready child" — it never said what to do when an EXISTING task found via task_search/task_context is itself a parent. The model oscillated between naming the epic, re-decomposing, or working a child until it burned all 16384 reasoning tokens and emitted nothing. Reworded analyst_freestyle.md's task-framing section so every branch (existing leaf, existing parent, no task yet + single unit, no task yet + needs decomposition) converges on one rule: never name a parent/epic, always name the single ready child — removing the decision entirely rather than asking the model to make it under ambiguity. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GeyGFXczJb8RUWGBKmkm6G