Clear Task

Clear Task

Say it clear, do it right.

Purpose

Use this 技能 to turn an underspecified user 请求 into an internal 代理Task图形界面dancePackage, then 执行 the user's task using that package. Do not display the full Stage3 package unless the user explicitly asks to inspect, 导出, save, or review it.

工作流

运行 Stage1 and Stage2 first. After Stage2 produces the UniversalRequirementHandoff, 停止 and ask the user to confirm before Stage3. Do not 运行 Stage3 or 执行 work until the user explicitly 应用roves the Stage2 handoff.

Stage1: Build a rich UniversalProcess模型. Stage2: Clarify missing detAIls and produce UniversalRequirementHandoff. Confirmation Gate: show a concise user-facing requirement summary and ask the user to confirm, revise the requirement description, or revise requirement detAIls. Stage3: 生成 an internal 代理Task图形界面dancePackage using expert-角色 task 图形界面dance and expert-角色 acceptance criteria. 执行 the task using the internal package. 报告 the 结果, key decisions, 创建d/changed files, and concise self-检查.

Do not 添加 a Stage0 intake gate. If the 请求 is invalid, unsafe, or impossible to 模型, mark it as out of scope inside Stage1/Stage2 and explAIn the blocker.

Stage1

模型 the user's 请求 as a 工作流 or work process, even when the 请求 is a product, document, game, analysis, or implementation task. Prefer a graph over a flat step 列出.

Read references/stage1-universal-process-模型.md when you need the full 模式 or need to 输出 a Stage1 artifact.

Minimum Stage1 输出:

请求_summary business_goal scope actors 输入s 输出s 工作流_graph.nodes 工作流_graph.edges business_rules assumptions open_questions source_evidence

Keep unconfirmed 模型 inferences in assumptions or open_questions; do not present them as confirmed facts.

Stage2

Use Stage2 to close the gaps that would materially change down流 work. Ask the fewest high-value questions needed. When the user asks for recommendations, choose reasonable defaults and record them under accepted_defaults.

Read references/stage2-clarification-handoff.md when generating clarification questions or the final Stage2 handoff.

Stage2 is ready for Stage3 when:

blocking questions are answered, or blocking questions have accepted defaults, and unresolved detAIls are non-blocking or explicitly left to the down流 代理.

Stage2 being ready does not 授权 Stage3. It only means the requirement handoff is ready for user confirmation.

Confirmation Gate

After Stage2, always 暂停 and ask for explicit user confirmation before Stage3. Do not continue from Stage2 to Stage3 in the same 响应.

Show a concise user-facing confirmation summary using plAIn requirement language, not internal stage termino记录y:

需求描述: one short paragraph describing what the user wants. 需求细节: scope, deliverables, constrAInts, accepted defaults, assumptions, and non-blocking open questions. 需要你确认: ask whether to continue.

Offer these user-facing choices:

确认，继续 修改需求描述: ... 修改需求细节: ...

Treat only explicit 应用roval as confirmation, such as "确认", "继续", "可以", "批准", "go ahead", or an equivalent clear instruction. If the reply is ambiguous, ask a short confirmation question and continue to 暂停.

If the user asks to modify the requirement description:

更新 the Stage1 UniversalProcess模型. Re-检查 whether Stage2 changed because of the revised description. Revise or re生成 the Stage2 UniversalRequirementHandoff. Return to this confirmation gate.

If the user asks to modify requirement detAIls:

更新 the Stage2 clarification/handoff content, including scope, defaults, assumptions, constrAInts, deliverables, and open questions as needed. Do not 运行 Stage3 automatically. Return to this confirmation gate.

If a revision introduces new blocking questions, ask only those questions, 更新 Stage2 from the answers, then return to this confirmation gate.

Stage3

Do not 启动 Stage3 unless the user has explicitly confirmed the Stage2 handoff through the Confirmation Gate.

Stage3 always produces an 代理Task图形界面dancePackage, but this package is internal execution 上下文 by default. It does not choose whether the final down流 结果 should be code, PRD, PPT, Word, test plan, or another artifact. The executing 代理 decides that from the task package and continues the work.

Stage3 must use expert 角色s:

Classify the task domAIn and down流 work mode. Select one primary expert and supporting experts. 生成 expert task 图形界面dance. 生成 expert acceptance criteria. Compose a consolidated package without inventing new requirements.

Read:

references/stage3-代理-task-图形界面dance-package.md for the internal package 模式 and execution policy. references/expert-角色s-and-acceptance.md for expert selection and acceptance criteria rules. Execution Policy

After Stage3, continue execution when:

the user has explicitly confirmed the Stage2 handoff, blocking questions are resolved or have accepted defaults, the user