Menu
Surface the agent's assumptions about a phase approach before planning
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | thrunt-list-phase-assumptions |
| description | Surface the agent's assumptions about a phase approach before planning |
| argument-hint | [phase] |
| allowed-tools | Read, Bash, Grep, Glob |
Purpose: Help users see what the agent thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt
<execution_context> @.github/thrunt-god/workflows/list-phase-assumptions.md </execution_context>
Phase number: $ARGUMENTS (required)Project state and huntmap are loaded in-workflow using targeted reads.
1. Validate phase number argument (error if missing or invalid) 2. Check if phase exists in huntmap 3. Follow list-phase-assumptions.md workflow: - Analyze huntmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps<success_criteria>
Show available THRUNT threat hunting commands and artifact layout
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
Publish a hunt as a case report, escalation, detection promotion, or leadership summary
