원클릭으로
thrunt-list-phase-assumptions
Surface the agent's assumptions about a phase approach before planning
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Surface the agent's assumptions about a phase approach before planning
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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
| 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>