/quick
Execute a quick task with THRUNT guarantees (atomic commits, state tracking) but skip optional agents
$ npx -y skills add backbay-labs/thrunt-god --agent claude-codeHow 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
/quick
Context preview
What this command does when you run it.
Execute a quick task with THRUNT guarantees (atomic commits, state tracking) but skip optional agents
Command definition
quick.mdname: thrunt:quick
description: Execute a quick task with THRUNT guarantees (atomic commits, state tracking) but skip optional agents
argument-hint: "[--full] [--discuss] [--research]"
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
- Task
- AskUserQuestion
<objective> Execute small, ad-hoc tasks with THRUNT guarantees (atomic commits, STATE.md tracking).
Quick mode is the same system with a shorter path:
- Spawns thrunt-hunt-planner (quick mode) + thrunt-telemetry-executor(s)
- Quick tasks live in `.planning/quick/` separate from planned phases
- Updates STATE.md "Quick Tasks Completed" table (NOT HUNTMAP.md)
**Default:** Skips research, discussion, plan-checker, and findings validation. Use when you know exactly what to do.
**`--discuss` flag:** Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront.
**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution findings validation. Use when you want quality guarantees without full milestone ceremony.
**`--research` flag:** Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach.
Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + findings validation. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/quick.md </execution_context>
<context> $ARGUMENTS
Context files are resolved inside the workflow (`init quick`) and delegated via `<files_to_read>` blocks. </context>
<process> Execute the quick workflow from @~/.claude/thrunt-god/workflows/quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits). </process>
Read more
name: thrunt:quick description: Execute a quick task with THRUNT guarantees (atomic commits, state tracking) but skip optional agents argument-hint: "[--full] [--discuss] [--research]" allowed-tools: - Read - Write - Edit - Glob - Grep - Bash - Task - AskUserQuestion
<objective> Execute small, ad-hoc tasks with THRUNT guarantees (atomic commits, STATE.md tracking).
Quick mode is the same system with a shorter path:
- Spawns thrunt-hunt-planner (quick mode) + thrunt-telemetry-executor(s)
- Quick tasks live in `.planning/quick/` separate from planned phases
- Updates STATE.md "Quick Tasks Completed" table (NOT HUNTMAP.md)
**Default:** Skips research, discussion, plan-checker, and findings validation. Use when you know exactly what to do.
**`--discuss` flag:** Lightweight discussion phase before planning. Surfaces assumptions, clarifies gray areas, captures decisions in CONTEXT.md. Use when the task has ambiguity worth resolving upfront.
**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution findings validation. Use when you want quality guarantees without full milestone ceremony.
**`--research` flag:** Spawns a focused research agent before planning. Investigates implementation approaches, library options, and pitfalls for the task. Use when you're unsure of the best approach.
Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + findings validation. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/quick.md </execution_context>
<context> $ARGUMENTS
Context files are resolved inside the workflow (`init quick`) and delegated via `<files_to_read>` blocks. </context>
<process> Execute the quick workflow from @~/.claude/thrunt-god/workflows/quick.md end-to-end. Preserve all workflow gates (validation, task description, planning, execution, state updates, commits). </process>
Threat hunting command system for agentic IDEs
Repo: backbay-labs/thrunt-god
Other commands on thrunt-god.
- /help
Show available THRUNT threat hunting commands and artifact layout
Open command - /map-environment
Map available telemetry, query surfaces, tenants, retention windows, and investigation blind spots
Open command - /new-case
Initialize a threat hunting case from a signal, detection, intel lead, or analyst suspicion
Open command - /new-program
Initialize a threat hunting program with an environment map, tool inventory, huntmap, and empty execution directories
Open command - /plan
Create phase plans for a threat hunt with exact telemetry tasks, receipts, and query outputs
Open command - /publish
Publish a hunt as a case report, escalation, detection promotion, or leadership summary
Open command

