Edge Diagnostics
Diagnoses stressed organizational relationships, handoffs, and system interfaces to resolve operational friction without personal blame.
Edge Diagnostics applies systems thinking to operational breakdowns by prioritizing edges—the relationships, handoffs, boundaries, and dependencies between teams, systems, and processes—over blaming individual nodes or contributors. When cross-functional friction arises, this skill guides Claude through analyzing interface tensions, decision latencies, broken feedback loops, and informal workarounds. It delivers a structured Edge Diagnostic Map that identifies symptoms, testable evidence, and small, high-impact behavioral repairs to restore alignment across complex team and software architectures.
Key Features
01Produces structured Edge Diagnostic Maps with symptoms, tensions, and validation criteria
02Separates relationship and interface friction from individual performance issues
03Maps relationship and interface dependencies across teams, tools, and processes
04Formulates small, testable, and actionable repairs to stabilize collaborative workflows
050 GitHub stars
06Pinpoints systemic tension points across handoffs, ownership boundaries, and decision rights
Use Cases
01Resolving recurring delivery delays and friction across engineering, QA, and product handoffs
02Diagnosing operational slowdowns caused by unclear ownership boundaries and decision latency
03Conducting blameless retrospectives and cross-functional operating issue investigations