creedants/pstack-t3

principle-never-block-on-the-human

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

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/creedants/pstack-t3 --skill principle-never-block-on-the-human

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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.

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli 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.

installazioni
1
GitHub Stars
5
Aggiornato
11 ott
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.

installazioni
1
GitHub Stars
5
Aggiornato
11 ott
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.

installazioni
1
GitHub Stars
5
Aggiornato
11 ott
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.

installazioni
1
GitHub Stars
5
Aggiornato
11 ott