/next
Automatically advance to the next logical step in the active hunt or THRUNT workflow
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/next
Context preview
What this command does when you run it.
Automatically advance to the next logical step in the active hunt or THRUNT workflow
Command definition
next.mdname: thrunt:next description: Automatically advance to the next logical step in the active hunt or THRUNT workflow allowed-tools: - Read - Bash - Grep - Glob - SlashCommand
<objective> Detect the current project or hunt state and automatically invoke the next logical workflow step. No arguments needed — reads `STATE.md`, `MISSION.md`, `HUNTMAP.md`, and phase directories to determine what comes next.
Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/next.md </execution_context>
<process> Execute the next workflow from @~/.claude/thrunt-god/workflows/next.md end-to-end. </process>
Repo: backbay-labs/thrunt-god
Other commands on thrunt-god.
map-environment
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
new-case
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
new-program
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
plan
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
publish
Publish a hunt as a case report, escalation, detection promotion, or leadership summary

