pi-squad

Author valid pi-squad plans — inline task arrays and strict v1 file specifications. Use when creating a squad plan, writing a squad spec JSON, choosing between inline tasks and specFile, computing specSha256, or debugging squad validation errors (must be array, SPEC_MALFORMED, SPEC_HASH_MISMATCH, Plan rejected).

Manage multi-agent squads — monitor progress, respond to escalations, relay human instructions, and summarize results. Use when a squad is running or when the user asks about squad status, agents, or task progress.

Code review methodology — two-pass review (correctness/scope, then over-engineering), surgical-change discipline, complexity findings with delete/stdlib/native/yagni/shrink tags, machine-parsed verdicts. Use when reviewing diffs, implementations, or pull requests.

Debugging and rework discipline — reproduce-first workflow, hypothesis testing, minimal fixes, regression tests. Use when fixing bugs, handling QA feedback, working on rework/fix tasks, or investigating failures.

Core communication protocol for multi-agent squad collaboration. Defines how agents talk to each other, signal status, and coordinate work.

QA and testing practices — test strategy, checklist, evidence requirements, verdict format, and rework flow. Use when verifying, testing, or reviewing implementations.

Multi-agent collaboration patterns — how to build on others' work, ask questions, share knowledge, and work as a team.

System architecture practices — project structure, API contracts, shared types, monorepo setup, and technical decision documentation. Use when designing system architecture, defining contracts between components, or setting up project structure.

Backend engineering practices — API design, database patterns, auth implementation, input validation, error handling, and security. Use when building APIs, servers, databases, or backend services.

Frontend engineering practices — React patterns, CSS/Tailwind, accessibility, state management, API integration, and responsive design. Use when building UIs, web apps, or frontend components.

Security audit checklist, vulnerability patterns, and remediation guidance. Use when reviewing code for security issues, hardening an application, or performing security verification.

Verify work before claiming completion — evidence-based discipline for multi-agent handoffs.