principle-never-block-on-the-human

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

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-never-block-on-the-human-mmdmcy
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/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/principle-never-block-on-the-human
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill principle-never-block-on-the-human-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that pause to ask "should I do X?" on every reversible decision stall pipelines and make the human the bottleneck. This Skill encodes an operating principle: proceed on reversible work, present the result, and let the human course-correct asynchronously. ## Core Features & Use Cases - Proceed-then-present pattern: Do the work, show the result, and explain the reasoning instead of asking for permission first. - Clear boundaries: Irreversible actions (force-push, deleting production data, sending external messages) still require confirmation; reversible actions (writing code, editing notes, splitting tasks) proceed without blocking. - Async supervision model: Design 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 refactors a module and splits a large task into subtasks without pausing, then presents the diff for the human to review and adjust afterward. ## Quick Start Apply the never-block-on-the-human principle so the agent proceeds on reversible work and only asks for confirmation on irreversible actions.

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 step?▼

Apply the never-block-on-the-human principle: the agent proceeds on reversible work, presents the result, and explains its reasoning. Confirmation is reserved only for irreversible actions like force-pushes 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 asynchronous human supervision in agent workflows?▼

Async supervision means the human reviews plans, diffs, and changes on their own schedule after the work is done. Workflows are designed for review-after-the-fact rather than real-time approval gates.

Why is blocking on human approval costly for agent pipelines?▼

Every permission pause stalls the pipeline and makes the human the bottleneck. Since code changes are reversible and reviewable, a wrong decision usually costs minutes to fix, while a blocked agent consumes scarce human attention.

Does this principle apply to product direction decisions?▼

No. Product direction still comes from the human; the principle governs execution only. Agents make reasonable implementation decisions and proceed, while strategic choices remain with the human.