principle-never-block-on-the-human

Guides agents to proceed on reversible work instead of pausing for human confirmation.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill principle-never-block-on-the-human-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-never-block-on-the-human
Source: https://github.com/gmackie/agent-skills/tree/main/skills/principle-never-block-on-the-human
Command: npx skills add https://github.com/gmackie/agent-skills --skill principle-never-block-on-the-human-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that stop to ask "should I do X?" on every reversible decision stall the pipeline and turn the human into a bottleneck. This Skill defines an execution principle so agents make reasonable decisions, proceed, and let the human course-correct after the fact. ## Core Features & Use Cases - Proceed-then-present pattern: Do the work, show the result, and explain the reasoning instead of asking for permission first. - Reversibility boundaries: Distinguishes reversible actions (write code, edit notes, split tasks) from irreversible ones (force-push, delete production data, send external messages) that still require confirmation. - Async supervision model: Designs workflows for review-after-the-fact so the human reviews plans, diffs, and changes on their own schedule. - Use Case: During an autonomous coding session, the agent needs to refactor a module. Instead of pausing to ask, it applies the refactor, logs the decision, and presents the diff for later review. ## Quick Start Apply the never-block-on-the-human principle and proceed with this reversible task without asking for confirmation first.

Frequently Asked Questions about principle-never-block-on-the-human

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop an AI agent from asking for permission on every task?▼

Apply a proceed-then-present principle: the agent does the reversible work, shows the result, and explains its reasoning. Confirmation is reserved only for irreversible actions like force-push or deleting production data.

When should an autonomous agent still ask for human confirmation?▼

Confirmation is required for irreversible actions such as force-pushing, deleting production data, or sending external messages. Reversible actions like writing code, editing notes, or splitting tasks should proceed without blocking.

What is the difference between reversible and irreversible agent actions?▼

Reversible actions can be cheaply undone or reviewed after the fact, such as code edits and task splits. Irreversible actions cause permanent or external effects, like data deletion or outbound messages, and need explicit approval.

Does this principle remove human oversight from agent workflows?▼

No. Supervision becomes asynchronous: the human reviews plans, diffs, and changes on their own schedule. Product direction still comes from the human; only execution stops blocking.

Why is blocking on questions costly in agent pipelines?▼

Every permission pause stalls the pipeline and makes the human the bottleneck. A wrong reversible implementation costs minutes to fix, while a blocked agent consumes scarce human attention to unblock.