What problem does it solve? Architecture discussions often end with vague diagrams, hand-waved abstractions, and unexamined failure modes that collapse during implementation. This Skill systematically stress-tests every component boundary, protocol, data path, and failure semantic until the design is unambiguous enough to implement without further questions. ## Core Features & Use Cases - Adversarial Seam Auditing: Applies a 5-point contract (transport, schema, failure semantics, concurrency, backpressure) to every boundary between components, rejecting vague terms like "standard auth" or "eventually consistent". - Structured 5-Phase Interrogation: Walks the design from product constraints and ingress write paths through async seams, failure modes, read paths, and auth/audit, asking at most 2 targeted questions per turn. - Live System Ledger & Mermaid Diagrams: Maintains a running seam status table and a Mermaid diagram where unverified paths are explicitly marked, ending with an implementation-ready blueprint artifact. - Use Case: Before building a new order-processing service, run an interrogation session to lock down the queue broker, idempotency strategy, retry policies, and transactional boundaries so engineers can implement without ambiguity. ## Quick Start Ask the agent to interrogate the architecture of your planned system, starting with the target audience, scale expectations, and the core write path.
