/manager
Interactive command center for managing multiple project or hunt phases from one terminal
$ 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
/manager
Context preview
What this command does when you run it.
Interactive command center for managing multiple project or hunt phases from one terminal
Command definition
manager.mdname: thrunt:manager
description: Interactive command center for managing multiple project or hunt phases from one terminal
allowed-tools:
- Read
- Write
- Bash
- Glob
- Grep
- AskUserQuestion
- Task
<objective> Single-terminal command center for managing a milestone or hunt campaign. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work. In hunt mode that means shape/plan/run; in THRUNT utility mode it means management, audit, and workspace flows.
Designed for power users who want to parallelize work across phases from one terminal: shape or discuss a phase while another plans or runs in the background.
**Creates/Updates:**
- No files created directly — dispatches to existing hunt or THRUNT commands and background Task agents.
- Reads `.planning/STATE.md`, `MISSION.md`, `HUNTMAP.md`, and phase directories for status.
**After:** User exits when done managing, or all phases complete and the appropriate publish/verify lifecycle is suggested. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/manager.md @~/.claude/thrunt-god/references/ui-brand.md </execution_context>
<context> No arguments required. Requires `MISSION.md`, `HUNTMAP.md`, and `STATE.md`.
Project context, phase list, dependencies, recommendations, and workflow mode are resolved inside the workflow using `thrunt-tools.cjs init manager`. No upfront context loading needed. </context>
<process> Execute the manager workflow from @~/.claude/thrunt-god/workflows/manager.md end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete. </process>
Read more
name: thrunt:manager description: Interactive command center for managing multiple project or hunt phases from one terminal allowed-tools: - Read - Write - Bash - Glob - Grep - AskUserQuestion - Task
<objective> Single-terminal command center for managing a milestone or hunt campaign. Shows a dashboard of all phases with visual status indicators, recommends optimal next actions, and dispatches work. In hunt mode that means shape/plan/run; in THRUNT utility mode it means management, audit, and workspace flows.
Designed for power users who want to parallelize work across phases from one terminal: shape or discuss a phase while another plans or runs in the background.
**Creates/Updates:**
- No files created directly — dispatches to existing hunt or THRUNT commands and background Task agents.
- Reads `.planning/STATE.md`, `MISSION.md`, `HUNTMAP.md`, and phase directories for status.
**After:** User exits when done managing, or all phases complete and the appropriate publish/verify lifecycle is suggested. </objective>
<execution_context> @~/.claude/thrunt-god/workflows/manager.md @~/.claude/thrunt-god/references/ui-brand.md </execution_context>
<context> No arguments required. Requires `MISSION.md`, `HUNTMAP.md`, and `STATE.md`.
Project context, phase list, dependencies, recommendations, and workflow mode are resolved inside the workflow using `thrunt-tools.cjs init manager`. No upfront context loading needed. </context>
<process> Execute the manager workflow from @~/.claude/thrunt-god/workflows/manager.md end-to-end. Maintain the dashboard refresh loop until the user exits or all phases complete. </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

