principle-never-block-on-the-human

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

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/jnyross/pstack-muse --skill principle-never-block-on-the-human-jnyross
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/jnyross/pstack-muse/tree/main/skills/principle-never-block-on-the-human
Command: npx skills add https://github.com/jnyross/pstack-muse --skill principle-never-block-on-the-human-jnyross

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 operating principle where 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. - Clear action 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: Structures 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 fixes a noticed bug without pausing, presenting the diff for review afterward rather than blocking mid-task. ## Quick Start Apply the never-block-on-the-human principle so the agent proceeds on reversible work and only asks before 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 permission for every change?

Adopt a proceed-then-present principle: the agent makes reasonable decisions on reversible work, completes it, and presents the result with 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. It is also appropriate when intent genuinely cannot be inferred from context, not for routine reversible edits.

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

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

How does asynchronous human supervision work with autonomous agents?

The human reviews plans, diffs, and changes on their own schedule after the work is done. Workflows are designed for review-after-the-fact so the agent stays unblocked and the pipeline never stalls waiting for permission.

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

Product direction still comes from the human, and irreversible or externally visible actions still require explicit confirmation. The principle governs execution only, not decision-making authority over goals or destructive operations.