AGENT SKILL

principle-never-block-on-the-human

Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.

License 许可
MIT
最近更新
2026-10-03
Stars
★ 0
Forks
0

01 前言 Front Matter

name
principle-never-block-on-the-human
description
Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.
disable-model-invocation
true

03 SKILL.md 正文

Never Block on the Human

The human supervises asynchronously. Agents must stay unblocked: make reasonable decisions, proceed, and let the human course-correct after the fact. Code is cheap. Waiting is expensive.

Why: Every permission pause stalls the pipeline and makes the human the bottleneck. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking.

Pattern:

  • Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain why.
  • Reserve questions for genuine ambiguity. Ask only when you truly cannot infer intent from context.
  • Make the system self-healing. When you notice a problem, log it and fix it in the next round.
  • Supervision is async. The human reviews plans, diffs, and changes on their own schedule. Design workflows for review-after-the-fact.
  • Code is cheap, attention is scarce. A wrong implementation costs minutes to fix. A blocked agent costs the human's attention to unblock.

Boundaries:

  • Authorization boundaries. Destructive actions and external messages require authorization for that action. Honor authorization already given; broad autonomy does not authorize sending messages. Keep the repository's core-record safeguards.
  • Reversible actions (write code, edit notes, split tasks) should proceed without blocking.
  • Product direction comes from the human; execution should not block.

04 同仓库更多 Skills