principle-never-block-on-the-human

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

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill principle-never-block-on-the-human-sma1lboy
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/Sma1lboy/rove/tree/main/.agents/skills/pstack/skills/principle-never-block-on-the-human
Command: npx skills add https://github.com/Sma1lboy/rove --skill principle-never-block-on-the-human-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents that pause to ask "should I do X?" on every reversible decision stall the pipeline and make the human the bottleneck. This Skill establishes 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 first, show the result, and explain the reasoning instead of asking for permission upfront. - Clear 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 Design: Frames human review as an after-the-fact activity over plans, diffs, and changes rather than a synchronous gate. - Use Case: An agent running parallel coding tasks in a multiplexer like Rove keeps executing task splits and code edits without waiting, while the human reviews diffs later on their own schedule. ## Quick Start Apply this principle by proceeding with the reversible task at hand and presenting the finished result for review instead of 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 keep an AI agent from constantly asking for permission?▼

Adopt a proceed-then-present principle: the agent makes a reasonable decision, completes the reversible work, and presents the result with its reasoning. Confirmation requests are reserved only for irreversible actions or genuine ambiguity that cannot be resolved from context.

When should an autonomous agent still ask for confirmation?▼

Confirmation is required for irreversible actions such as force-pushing, deleting production data, or sending external messages. It is also appropriate when intent genuinely cannot be inferred from context, but not for routine reversible decisions.

What counts as a reversible action for an AI agent?▼

Reversible actions include writing code, editing notes, and splitting tasks, since these can be reviewed and corrected after the fact. A wrong implementation costs minutes to fix, while a blocked agent costs the human's attention to unblock.

How does asynchronous human supervision work with coding agents?▼

The human reviews plans, diffs, and changes on their own schedule rather than gating each step. Agents log problems they notice and fix them in the next round, making the workflow self-healing instead of dependent on synchronous approval.

What are the limits of the never-block-on-the-human principle?▼

The principle covers execution only; product direction still comes from the human. It does not authorize irreversible or externally visible actions without confirmation, and it does not apply when intent is genuinely ambiguous.