Skip to main content
Back to Prompt Library
implementation

Initialize AutoGen Hardware Postmortem Team

Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.

Linked challenge: AutoGen Hardware Kernel Postmortem Analyzer & Fault Injector

Format
Code-aware
Lines
14
Sections
4
Linked challenge
AutoGen Hardware Kernel Postmortem Analyzer & Fault Injector

Prompt source

Original prompt text with formatting preserved for inspection.

14 lines
4 sections
No variables
0 checklist items
import autogen

config_list = [{'model': 'gpt-4o', 'api_key': 'ENV_KEY'}]

# Diagnostic Agent specializing in CUDA/Triton log parsing
kernel_expert = autogen.AssistantAgent(
    name="KernelExpert",
    system_message="You analyze CUDA stack traces, Triton PTX dumps, and NVML logs to identify GPU kernel failure causes.",
    llm_config={'config_list': config_list}
)

# System Recovery Agent
ops_engineer = autogen.AssistantAgent(
    name="OpsEngineer",
    system_message="You generate precise remediation steps (draining node, patching kernel args, dynamic fallback).",
    llm_config={'config_list': config_list}
)

Adaptation plan

Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.

Keep stable

Hold the task contract and output shape stable so generated implementations remain comparable.

Tune next

Update libraries, interfaces, and environment assumptions to match the stack you actually run.

Verify after

Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.