creedants/pstack-t3

principle-never-block-on-the-human

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

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/creedants/pstack-t3 --skill principle-never-block-on-the-human

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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.

Related by task

from this repository

More skills

All skills
creedants
Community

correct

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

installs
1
GitHub stars
5
Updated
Oct 11
creedants
Community

landing

Let many agents write to one repository at once without collisions: a per-repository landing contract, path leases claimed before work starts, one queue that is the only writer to trunk, and a machine-wide slot governor for builds and tests. Use for 'landing', 'land this', 'merge queue', 'many agents on one repo', 'where does this work land', or before any coordinator (brigade, Orchestrate, Autopilot, swarm) delegates writing work in parallel.

installs
1
GitHub stars
5
Updated
Oct 11
creedants
Community

principle-exhaust-the-design-space

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

installs
1
GitHub stars
5
Updated
Oct 11
creedants
Community

principle-foundational-thinking

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes obvious.

installs
1
GitHub stars
5
Updated
Oct 11