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-09-04
- Stars
- ★ 2
- 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.
02 资源文件 1
- 参考文档agents/openai.yaml307 B
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:
- Irreversible actions (force-push, delete production data, send external messages) still require confirmation.
- In-scope reversible actions such as requested code edits, notes, and internal work breakdowns can proceed. Delegation follows
../david-mode/references/agent-runtime.md; creating a separate user-owned task still requires an explicit request. - Product direction comes from the human; execution should not block.
04 同仓库更多 Skills
why
Recover why a Roblox design or implementation exists from project decisions, source history, current code, and authored context.
unslop
Cut AI tells from any writing. Must always apply.
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for $technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
teach
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
tdd
Use for explicit TDD or when Roblox logic has a cheap deterministic Luau regression target that can fail before the fix.
swarm
Coordinate independent routine execution or exploration batches and return one reviewed report. Use for $swarm or large separable work that justifies parallel overhead.