with one click
thrunt-add-backlog
Add an idea to the backlog parking lot (999.x numbering)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Add an idea to the backlog parking lot (999.x numbering)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | thrunt-add-backlog |
| description | Add an idea to the backlog parking lot (999.x numbering) |
| argument-hint | <description> |
| allowed-tools | Read, Write, Bash |
Read HUNTMAP.md to find existing backlog entries:
cat .planning/HUNTMAP.md
Find next backlog number:
NEXT=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" phase next-decimal 999 --raw)
If no 999.x phases exist, start at 999.1.
Create the phase directory:
SLUG=$(node ".github/thrunt-god/bin/thrunt-tools.cjs" generate-slug "$ARGUMENTS")
mkdir -p ".planning/phases/${NEXT}-${SLUG}"
touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
Add to HUNTMAP.md under a ## Backlog section. If the section doesn't exist, create it at the end:
## Backlog
### Phase {NEXT}: {description} (BACKLOG)
**Goal:** [Captured for future planning]
**Hypotheses:** TBD
**Plans:** 0 plans
Plans:
- [ ] TBD (promote with /thrunt-review-backlog when ready)
Commit:
node ".github/thrunt-god/bin/thrunt-tools.cjs" commit "docs: add backlog item ${NEXT} — ${ARGUMENTS}" --files .planning/HUNTMAP.md ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
Report:
## 📋 Backlog Item Added
Phase {NEXT}: {description}
Directory: .planning/phases/{NEXT}-{slug}/
This item lives in the backlog parking lot.
Use /hunt-shape-hypothesis {NEXT} to explore it further.
Use /thrunt-review-backlog to promote items to active milestone.
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