/list-phase-assumptions
Surface Claude's assumptions about a phase approach before planning
$ 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
/list-phase-assumptions
Context preview
What this command does when you run it.
Surface Claude's assumptions about a phase approach before planning
Command definition
list-phase-assumptions.mdname: thrunt:list-phase-assumptions
description: Surface Claude's assumptions about a phase approach before planning
argument-hint: "[phase]"
allowed-tools:
- Read
- Bash
- Grep
- Glob
<objective> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
Purpose: Help users see what Claude 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 </objective>
<execution_context> @~/.claude/thrunt-god/workflows/list-phase-assumptions.md </execution_context>
<context> Phase number: $ARGUMENTS (required)
Project state and huntmap are loaded in-workflow using targeted reads. </context>
<process> 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 </process>
<success_criteria>
- Phase validated against huntmap
- Assumptions surfaced across five areas
- User prompted for feedback
- User knows next steps (discuss context, plan phase, or correct assumptions)
</success_criteria>
Read more
name: thrunt:list-phase-assumptions description: Surface Claude's assumptions about a phase approach before planning argument-hint: "[phase]" allowed-tools: - Read - Bash - Grep - Glob
<objective> Analyze a phase and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
Purpose: Help users see what Claude 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 </objective>
<execution_context> @~/.claude/thrunt-god/workflows/list-phase-assumptions.md </execution_context>
<context> Phase number: $ARGUMENTS (required)
Project state and huntmap are loaded in-workflow using targeted reads. </context>
<process> 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 </process>
<success_criteria>
- Phase validated against huntmap
- Assumptions surfaced across five areas
- User prompted for feedback
- User knows next steps (discuss context, plan phase, or correct assumptions)
</success_criteria>
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

