Menu
Validate hunt conclusions against receipts, contradictory evidence, and success criteria
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle 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 | hunt-validate-findings |
| description | Validate hunt conclusions against receipts, contradictory evidence, and success criteria |
| argument-hint | [phase] |
| allowed-tools | Read, Bash, Write, AskUserQuestion |
FINDINGS.md and EVIDENCE_REVIEW.md remain the source of truth for validation.
Creates or updates:
.planning/FINDINGS.md.planning/EVIDENCE_REVIEW.md.planning/STATE.mdAfter this command: Run /hunt-publish.
<execution_context> @.github/thrunt-god/workflows/hunt-validate-findings.md @.github/thrunt-god/templates/findings.md @.github/thrunt-god/templates/evidence-review.md </execution_context>
Execute the validation workflow from @.github/thrunt-god/workflows/hunt-validate-findings.md. Mark each hypothesis as supported, disproven, or inconclusive. Call out evidence gaps explicitly.