pi-crew

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.

Pi TUI crew widget data sources, display priority, and rendering performance.

Multi-phase orchestration for planners and executors.

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 choices, security tradeoffs, or plan reviews where single-perspective analysis is insufficient.

Background worker, heartbeat, stale-run, crash-recovery, and deadletter workflow. Use when debugging stuck/dead workers or changing async run reliability.

Child Pi worker spawning, lifecycle callbacks, and failure modes.

Use when constructing worker prompts, reading artifacts/logs, summarizing runs, compacting context, or handing work between agents.

Subagent/team delegation workflow.

Structured event logging for worker lifecycle, live agents, crash recovery.

Commit and release hygiene for safe version-control work.

Live agent registration, workspace isolation, termination, and eviction workflow.

Interactive waiting-task and mailbox workflow.

Model routing, parent context, thinking level, and prompt construction workflow. Use when changing model fallback, child Pi args, inherited context, task prompts, or compact-read behavior.

Multi-perspective code review with simpler-alternative pass.

Metrics, diagnostics, correlation, retry, deadletter, and recovery evidence workflow.

Session ownership and authorization workflow.

Pi extension lifecycle and registration patterns.

Write engineering RCA record after bug is fixed.

Read-only exploration and audit workflow.

Use when a goal, issue, roadmap item, review finding, or user request must become actionable worker tasks.

pi-crew resource and configuration discovery workflow.

Safe read-only navigation of pi-crew run state.

Safe shell-command workflow.

Outsider-perspective review questioning intent before tracing code.

Use when reviewing delegation, skill loading, tool access, worker prompts, artifacts, runtime config, state, ownership, or subprocess execution.

Durable state mutation and locking workflow.

Four-phase debugging discipline with refuse gates.

Evidence before claims.

Workspace isolation boundaries.

Conflict-safe git worktree workflow.