Principle Never Block On The Human Skill for Claude
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/michael-denyer/pstack-claude --skill principle-never-block-on-the-humanThe instruction itself
1 sections, as written by the authorNever 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.
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 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. Design workflows for review-after-the-fact.
Boundaries:
- Irreversible actions (force-push, delete production data, send external messages) still require confirmation.
- Reversible actions (write code, edit notes, split tasks) should proceed without blocking.
- Product direction comes from the human; *execution* should not block.
How to use it
Take michael-denyer/principle-never-block-on-the-human from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.