asklisted

Use this when the user asks you to delegate with CCB, or when project memory says to use CCB `ask` for collaboration. ## Choose The Mode First - Normal user turn, direct chat request, release handoff, review handoff, or any context that is not a CCB-delivered active parent job: use plain `ask`. - Do not probe `--callback`. If you are unsure whether there is an active parent job, there is not one; use plain `ask`. - Use `--callback` only when this exact turn is an active CCB task and the child result is required before you can finish that parent task. After callback submit, stop; CCB will deliver the child result as a continuation. - If CCB says `ask --callback requires an active parent job`, the mode choice was wrong. For a user-requested delegation, submit once with plain `ask` and stop. - Use `--silence` only for independent work where success does not need a reply body. Failures, blockers, or required next actions should still surface. - Use `--compact` when the caller wants distilled findings, status, risks, blockers, or next actions. - Use `--artifact-request` when the task body is large or must be passed by file. CCB stores the request in a text artifact and sends the target only a file reference. - Use `--artifact-reply` when the caller or callback continuation should receive the target result as a text artifact path, even if the target replies inline. - Use `--artifact-io` when both the request and reply should be artifact-backed. - `--artifact-*