Analyze cross-system issues to diagnose architecture-level root causes and systemic risks.
npx skills add https://github.com/benediktms/overmind --skill cortex-benediktms
Please help me install this Agent Skill. Skill: cortex Source: https://github.com/benediktms/overmind/tree/main/cli/claudecode-plugin/skills/cortex Command: npx skills add https://github.com/benediktms/overmind --skill cortex-benediktms
Evaluates cross-system problems by providing architecture-focused analysis to identify root causes, design trade-offs, and safe remediation strategies that preserve system behavior.
Provide a concise architecture-focused plan to resolve the cross-system issue and preserve module behavior.
High-intent search queries and answers about installing and using this skill.
To diagnose intermittent failures across multiple subsystems, perform an architecture-focused analysis to identify subsystem dependencies, integration risks, and root causes while preserving system behavior. This evaluates trade-offs and outlines verifiable, integration-safe remediation steps.
Analyzing race conditions and deadlocks during a cross-system refactor requires evaluating design options for their impact on correctness and performance. Compare trade-offs to document rationale and ensure behavior preservation across module boundaries before applying remediation steps.
To evaluate design trade-offs for cross-boundary changes, compare options based on their impact on correctness, performance, and maintainability. Document the rationale to ensure behavior is preserved across module boundaries during integration.
You need architecture-level analysis for cross-system integration risks when diagnosing intermittent failures, evaluating refactor risks, or making cross-boundary changes where multiple subsystems are affected. It detects root causes and subsystem dependencies to ensure safe remediation.
Without documenting design rationale, analyzing systemic risks lacks verifiable, integration-safe remediation steps. This prevents proper evaluation of trade-offs needed to preserve system behavior across module boundaries when addressing root causes.
haJ1tAnalyze memory dumps and system logs to construct event timelines and identify root causes.
AZANIRAnalyze CI history to classify flaky tests into four failure patterns.
iCesofTIdentify and fix thread-safety, race conditions, and deadlock risks in Java concurrent code.
vadimcomanescuGenerate feature specifications, design plans, and implementation tasks.
