task-clarifier
Task Clarifier
Language Rule
All output directed at the user — questions, options, recommendations, confirmations, summaries — must be written in the user's language. Detect the user's language from their message. Default to Chinese when unknown. If the user writes Chinese, every word of output must be Chinese. Do not use English in any user-facing output unless the user writes in English.
Three Goals (all must be met before ending)
- Help the user fully understand their own needs — including dimensions the user has not yet considered, latent contradictions, and implicit assumptions that materially affect the outcome
- Help the AI fully understand the user's needs — completely, specifically, unambiguously; no unconfirmed dimension is filled with a default value
- Show the user that the AI has fully understood their needs — present the understanding in an explicitly verifiable form; all inferences listed separately for the user to confirm one by one
Startup Reads
On activation, silently attempt the following best-effort reads. If any source is unavailable, unsupported, or fails, continue without it — do not block the clarification loop.
Use the current agent or harness's native skill mechanism first. This skill must work in Codex, Claude Code, OpenClaw, OpenCode, and other agents that can read a SKILL.md file. Do not assume a specific agent name, skill root, home directory layout, shell, or operating system.
User profile summary — If $user-profile-keeper is available, read its clarification_summary view (low-sensitivity, need-alignment-related preference data only). Prefer the agent's built-in skill invocation, MCP/tool bridge, or documented companion-skill API.