Background worker, heartbeat, stale-run, crash-recovery, and deadletter workflow. Use when debugging stuck/dead workers or changing async run reliability. When NOT to use: pure investigation without async context (use read-only-explorer); one-shot fixes that don't need recovery infrastructure.
Child Pi worker spawning, lifecycle callbacks, and failure modes. When NOT to use: non-Pi subprocess execution (use safe-bash); for general async reliability (use async-worker-recovery).
Use when constructing worker prompts, reading artifacts/logs, summarizing runs, compacting context, or handing work between agents. When NOT to use: tasks without artifact/context concerns; pure code questions (use read-only-explorer).
Spawn 3 adversarial subagents (Skeptic, Pragmatist, Critic) to evaluate a decision, architecture choice, or plan. Anti-anchoring: each role receives ONLY the question, not conversation history. Aggregates votes into consensus recommendation with dissent tracking. Use when facing critical decisions, architecture…
Distill a person's (or field's) thinking into a runnable pi skill — research, extract, validate, generate. REQUIRED — read the full skill file first (multi-phase protocol with machine-checked gates); run the validate-run script on before claiming done — ALL-GREEN required. When NOT to use: software engineering…
Distill software engineering expertise — an engineer's judgment, a codebase's conventions, or a domain's practice — and APPLY it to a TARGET project (never outputs a reusable skill file). REQUIRED — read the full skill file first (multi-phase protocol with machine-checked gates); run the validate-run script on before…
Structured event logging for worker lifecycle, live agents, crash recovery. When NOT to use: high-level metrics dashboards (use observability-reliability); for runtime state inspection (use runtime-state-reader).
Commit and release hygiene for safe version-control work. When NOT to use: experimental branches (use worktree-isolation); force-push or history rewrites (use scrutinize first).
Iterative multi-round codebase audit with diminishing-returns detection. Run 5-20+ rounds, each focusing on one specific area. Built from 19 rounds of dogfooding pi-crew on itself. When NOT to use: one-shot review (use multi-perspective-review); investigation with single round (use read-only-explorer).
Live agent registration, workspace isolation, termination, and eviction workflow. When NOT to use: static extension registration patterns (use pi-extension-lifecycle); ownership disputes (use ownership-session-security).
Model routing, parent context, thinking level, and prompt construction workflow. Use when changing model fallback, child Pi args, inherited context, task prompts, or compaction/compact-string behavior. When NOT to use: project-level config (use resource-discovery-config); routing for non-pi-crew agents.
Multi-perspective code review with simpler-alternative pass. When NOT to use: deep adversarial analysis (use council); simple code review without quality concerns.
Metrics, diagnostics, correlation, retry, deadletter, and recovery evidence workflow. When NOT to use: one-off event capture (use event-log-tracing); pure recovery logic (use async-worker-recovery).
Multi-phase orchestration for planners and executors. When NOT to use: single-task edits (use delegation-patterns); pure read-only audits (use read-only-explorer); one-shot questions (use ask).
Session ownership and authorization workflow. When NOT to use: general session lifecycle questions (use live-agent-lifecycle); for non-session auth issues.
Pi extension lifecycle and registration patterns. When NOT to use: single registration event (use direct API calls); for child worker lifecycle (use child-pi-spawning).
Write engineering RCA record after bug is fixed. When NOT to use: unresolved bugs (use systematic-debugging first); minor fixes that don't warrant RCA.
Read-only exploration and audit workflow. When NOT to use: any task that needs write actions; deep adversarial analysis (use council); quick one-line lookups (use bash directly).
Use when a goal, issue, roadmap item, review finding, or user request must become actionable worker tasks. When NOT to use: already-decided work that just needs execution; tasks so simple they fit one sentence.
Deep-research skill combining iterative depth, structured+validated output, rigor mechanisms, anti-thrash, and pi-native hooks for general deep research. REQUIRED — read the full skill file first (iterative-depth protocol with rigor scripts); run verifycitations and sourceevaluator on your output before claiming done.…
Safe read-only navigation of pi-crew run state. When NOT to use: write actions or mutations (use state-mutation-locking); configuration changes (use resource-discovery-config).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: