principle-never-block-on-the-human

Apply when tempted to ask 'should I do X?' on reversible work.

4,954
installs: 0 up / 0 down, score 0.00
votes: 2,555
repo stars
Updated: less than a month ago
In the catalog since: 5 Oct 2026
From: backnotprop/pstack

Get it through your agent npx skills add backnotprop/pstack@principle-never-block-on-the-human

Skill instructions

Rendered from the published SKILL.md, 10 lines.

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.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "principle-never-block-on-the-human"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository backnotprop/pstack
Listing on skills.sh

From backnotprop/pstack via skills.sh

Related skills

principle-never-block-on-the-human
Apply when tempted to ask 'should I do X?' on reversible work.
4,097 installs
principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
4,973 installs
principle-laziness-protocol
Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.
4,261 installs
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
4,934 installs
day1-onboarding
AI Native Camp Day 1 온보딩. Claude와 대화하면서 Claude Code를 익힌다. "1일차", "Day 1", "온보딩" 요청에 사용.
1,565 installs

More from backnotprop/pstack

unslop
Cut AI tells from any writing.
6,352 installs
how
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
5,487 installs
principle-fix-root-causes
Apply when debugging. Trace each symptom back to the first place the system went wrong and fix it there. A guard is a fix only when the state it handles is legitimate.
5,420 installs
why
Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.
5,403 installs
technical-writing
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
5,318 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.