
Analyze Liza agents logs
Coordinate Pairing-mode doer/reviewer sessions through a Markdown blackboard. Use when the user invokes /adversarial-pairing with role and blackboard-path arguments or asks multiple pairing agents to coordinate plan review, implementation, staged code review, and follow-up review rounds without Liza multi-agent mode.
Code Review Protocol
Analyze Liza `.liza/agent-prompts/` and `.liza/agent-outputs/` from a context-engineering perspective: prompt payload shape, context budget use, cacheability, duplicated or missing context, instruction hierarchy, tool-output pressure, role-specific context fit, and prompt-output feedback loops. Use when diagnosing agent context bloat, prompt drift, poor agent handoffs, repeated misunderstandings, excessive tool output, or whether Liza agents received the right information at the right time.
Transform requirements into user stories for coding tasks
Transform vision documents into structured epics that bound story-writing
Context-efficient delegation to subagents (read-only default, READ-WRITE opt-in)
Quantitative and qualitative code quality assessment with prioritized refactoring recommendations
Software Architecture Review Protocol
Define component boundaries, interfaces, and structural decisions for a change
Backfill missing specifications, reconcile spec/code drift, maintain changelog.
Specification Review Protocol
Systemic Coherence and Risk Analysis
Find bugs by writing tests that should pass but don't. Invoke manually on user-chosen scope (commits, files, or coverage threshold). Outputs red tests with structured rationale. Use when user asks to "stress-test", "find bugs in", "attack", or "break" code.
Test Protocol
Pre-commit Clean Code refactoring
Black-Box Red Testing — red tests that expose real bugs
Summarize artifacts produced by liza agents for human checkpoint review
explain complex ideas as Richard Feynman
Backfill function-level contracts (docstrings, type annotations) where missing. Report unresolvable gaps with misuse scenarios. Incremental by default (state-driven).
Debugging Protocol
Transform requirements into precise specifications for coding tasks
Surface alternatives — different ways to address the same need.
Capture project-specific operational lessons from mistakes, discoveries, and hard-won insights
Backfill missing ADR from git history and documentation