kookr-spawn-child-tasklisted

# Spawn Child Task When you need to delegate follow-up work to a separate Kookr task (e.g., "this needs a separate PR", "fix that in a new task"), use the Kookr HTTP API to create a child task. ## When to use - The user asks you to handle something "in a new task" or "separately" - You identify follow-up work that should be tracked independently - A refactor, fix, or investigation is outside the scope of your current task ## Scope discipline — the child does ONE thing A child task must have a single, narrowly-defined job. If the overall work has multiple phases — evaluate → decide → adjust → evaluate again — orchestrate those phases **from the parent**: spawn one child for one evaluation, wait for its result, adjust state in the parent based on the result, then spawn the next child. **Do not encode iteration or orchestration logic inside the child prompt.** In particular: - Do not ask the child to re-run a subagent N times with a file that the child itself is supposed to rewrite between runs. File-based prompt reloads across Agent subagent invocations are not reliably picked up within a single child session — the second invocation may see the same prompt the first one saw. - Do not ask the child to "iterate until the metric passes". That bundles three responsibilities (evaluate, judge, adjust) that should live with the decision authority (the parent) rather than the evaluation worker (the child). - Do not ask the child to open PRs based on its own output unless the par