Claude Skills by LarryStanley

Dispatch to pi behind a critic gate — a second, independent pi session judges the work against a contract written up front, and rejections go back for a bounded number of rounds

Use when delegating coding work to the local pi agent to cut cost, or when you are about to hand-write source or test files yourself instead of specifying them, or when a small-model agent reads files endlessly without ever writing, times out having produced nothing, or keeps reasoning forever even though thinking was turned off.

Think a problem through with pi as a second opinion, over as many turns as it takes

Check pi's dispatch environment (which provider/model a dispatch reaches, the thinking binding, the co-pilot guard)

Switch this project's pi dispatch mode (off / soft / strict)

Get a one-time bypass so the next Write/Edit is not blocked by strict mode (for probing)

Have pi review code as a second opinion, then adjudicate its findings

First-run guided setup for pi-delegate — checks pi and its provider, explains the discipline modes and asks which to use, offers to fix detected problems, offers a verification dispatch, and points to what's next

Add a live pi dispatch indicator to the Claude Code status line, composed with whatever status line the user already has