ask

Use this skill when the user asks you to delegate with CCB, or when project memory says to use CCB `ask` for collaboration. ## Decision Card Before every ask, decide: 1. Need delegation? If no, answer directly. 2. Result intent: - `--silence`: publish/execute task; success result not needed. Failures, blockers, risks, or required next actions still surface. - `--compact`: result wanted, but only distilled findings/status/risks/blockers/next actions. - `+ --artifact-reply`: consultation/analysis/report where full text should be preserved. - plain `ask`: short question or short handoff where inline text is enough. - `--chain`: active CCB parent job + child result required to finish. Combine with `--compact` or `--artifact-reply` as needed. Submit, then stop for continuation. 3. Request fidelity: - `+ --artifact-request`: exact transient input (logs/output/diffs/copied contents/config/JSON/YAML/table/structured text). Prefer repo paths when the target can read files directly. - `--artifact-io`: request and reply both need artifacts. ## Guardrails - Do not probe `--chain`; if unsure there is an active parent job, use plain `ask`. - If CCB says `ask --chain requires an active parent job`, retry once with plain `ask` for user-requested delegation. - `--chain` and `--silence` usually conflict; avoid mixing unless explicit. - Avoid `--silence --artifact-reply`; silence means no caller result needed; artifact-reply prese...