Back to Prompt Library
implementation
Implementing Extended Thinking for Alert Correlation
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Autonomous Cloud Security Triage Agent
Format
Text-first
Lines
2
Sections
2
Linked challenge
Autonomous Cloud Security Triage Agent
Prompt source
Original prompt text with formatting preserved for inspection.
2 lines
2 sections
No variables
0 checklist items
Enhance your Claude agent to perform multi-step extended thinking when triaging alerts. Instead of direct classification, the agent should first hypothesize potential causes, then use tools to gather evidence, and finally deduce the actual threat. The `reasoning_path` in the output should reflect these steps. Introduce a new tool, `get_process_hash(process_name: str)`, which simulates getting a hash to feed into `threat_intel_lookup`. Consider how to guide Claude Opus 4.1 to articulate its thought process effectively. Think about how the agent would decide *when* to use each tool in its reasoning flow.
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.