principle-never-block-on-the-human — Claude Code skill
Instructs coding agents to execute reversible changes immediately instead of asking for approval. Useful for autonomous sessions under asynchronous supervision.
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a claude-codeWhat principle-never-block-on-the-human does
The skill establishes an autonomy rule: agents must remain unblocked when dealing with reversible work. Instead of asking "should I do X?", the agent executes the change and explains the reasoning afterwards. Code edits are reviewable and easy to roll back. A mistaken edit usually costs less than waiting for human intervention.
The guideline sets a strict boundary between reversible and irreversible actions. Modifying source files or breaking down tasks proceeds without pauses. Destructive actions stay gated. Pushing with --force or deleting production data still demands explicit confirmation.
The frontmatter specifies disable-model-invocation: true, so this functions as a behavioral rule rather than an automated tool script. When the agent spots a defect, it logs the problem and applies a fix in the subsequent cycle.
What it helps with
- prevent agents from halting execution to ask permission for code edits
- enable asynchronous agent supervision without idle waiting periods
- allow the agent to log issues and apply self-healing fixes in the next pass
- protect production environments by requiring confirmation for irreversible actions
Example prompts for the agent
- Refactor the authentication flow following principle-never-block-on-the-human
- Split the task into subtasks and proceed with code edits without waiting for approval
How to install principle-never-block-on-the-human
1Skills CLI (Vercel)
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a claude-code2Manually: put the files in place
~/.claude/skills/principle-never-block-on-the-human/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/principle-never-block-on-the-human/
1Skills CLI (Vercel)
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a codex2Manually: put the files in place
.agents/skills/principle-never-block-on-the-human/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a cursor2Manually: put the files in place
.cursor/skills/principle-never-block-on-the-human/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install backnotprop/pstack principle-never-block-on-the-human2Manually: put the files in place
.github/skills/principle-never-block-on-the-human/SKILL.md1Skills CLI (Vercel)
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a gemini-cli2Platform CLI
gemini skills install https://github.com/backnotprop/pstack --path skills/principle-never-block-on-the-humanManually: put the files in place
.devin/skills/principle-never-block-on-the-human/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about principle-never-block-on-the-human
How to install principle-never-block-on-the-human in Claude Code?
Run npx skills add backnotprop/pstack --skill principle-never-block-on-the-human -a claude-code in your terminal.
What does principle-never-block-on-the-human do?
It instructs agents to execute reversible work like code changes without stopping for permission. The human reviews results after the work finishes.
Which actions still require human confirmation?
Irreversible actions remain blocked without human approval. Examples include force-pushing branches, deleting production data, and sending external messages.
Source text
SKILL.md · MIT
--- name: principle-never-block-on-the-human description: "Apply when tempted to ask 'should I do X?' on reversible work." disable-model-invocation: true --- # Never 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. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking. - Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain why. - Make the system self-healing. When you notice a problem, log it and fix it in the next round. - 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.
© backnotprop · MIT · backnotprop/pstack