grill-each-other

Each agent in a local fleet — Claude sessions on different machines, mixed-model agents, or whatever's in play — independently writes a short "what I know and what I'm working on" report to a shared directory. One reader collates them into a roundup. No grilling, no consensus, no merging. Use when you want visibility across a multi-agent fleet, or the user mentions "fleet show and tell", "agent roundup", "what does each agent know", or "round-robin status from the agents".

Reference for the scholastic + Greek vocabulary used in peer-grill and grill-me-agents protocols. Use when an agent needs to know what ELENCHOS, QUAESTIO, SED-CONTRA, RESPONDEO, or ALETHEIA mean as grill-log tags, or when authoring a structured disputation.

Use when the fleet must formally sign off on an artifact — a converged grill result, a vault doc, an ADR, a convention, or a proposition — and one agent's or a pair's approval is not enough and you need fleet-wide consensus. Use when chaining ratification onto a finished grill, or when a decision needs N-agent attestation or approval with dissent recorded rather than overruled.

Interview the user relentlessly about a multi-agent collaboration design until every role, handoff, and failure mode is resolved. Use when the subject is multi-agent collaboration, subagent orchestration, fleet topology, or agent-roster design — prefer this over `grill-me` whenever multiple agents are involved. Triggers: "grill my agent topology", "grill my multi-agent design", "stress-test agent collaboration", "interrogate the agent roster", "design subagent orchestration". Do NOT use for greenfield non-agent plan grilling (use `grill-me`) or when the agent stack already exists in the codebase and you want to stress-test a change to it (use `grill-me-with-agents`).

Code-aware variant of grill-me-agents — interrogates a multi-agent design while continuously cross-referencing existing agent definitions, skills, prompts, and tool configs in the repo. Use ONLY when the agent stack is already implemented in the repo and you want to stress-test a *change* to it (versus designing from scratch — use `grill-me-agents` for greenfield). Triggers: "grill the existing agent stack", "stress-test the agent stack", "grill the implemented agents", "audit the agent topology against code". Do NOT use for greenfield agent design (use `grill-me-agents`) or for two agents grilling each other (use `peer-grill`).