Get Anything Done

Create, list, or resume persistent context threads. Threads are lightweight cross-session knowledge stores for work that spans multiple sessions but doesn't belong to any specific phase.

Parse $ARGUMENTS to determine mode:

**If no arguments or $ARGUMENTS is empty:**

List all threads:

ls .planning/threads/*.md 2>/dev/null

For each thread, read the first few lines to show title and status:

## Active Threads

| Thread | Status | Last Updated |
|--------|--------|-------------|
| fix-deploy-key-auth | OPEN | 2026-03-15 |
| pasta-tcp-timeout | RESOLVED | 2026-03-12 |
| perf-investigation | IN PROGRESS | 2026-03-17 |

If no threads exist, show:

No threads found. Create one with: /gad:thread <description>

**If $ARGUMENTS matches an existing thread name (file exists):**

Resume the thread — load its context into the current session:

cat ".planning/threads/${THREAD_NAME}.md"

Display the thread content and ask what the user wants to work on next. Update the thread's status to IN PROGRESS if it was OPEN.

**If $ARGUMENTS is a new description (no matching thread file):**

Create a new thread:

Generate slug from description:

SLUG=$(gad-tools generate-slug "$ARGUMENTS" --raw)

Create the threads directory if needed:
```
mkdir -p .planning/threads
```

Write the thread file:

cat > ".planning/threads/${SLUG}.md" << 'EOF'
# Thread: {description}

## Status: OPEN

## Goal

{description}

## Context

*Created from conversation on {today's date}.*

## References

- *(add links, file paths, or issue numbers)*

## Next Steps

- *(what the next session should do first)*
EOF

If there's relevant context in the current conversation (code snippets, error messages, investigation results), extract and add it to the Context section.

Commit:

gad-tools commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"

Report:

## 🧵 Thread Created

Thread: {slug}
File: .planning/threads/{slug}.md

Resume anytime with: /gad:thread {slug}

- Threads are NOT phase-scoped — they exist independently of the roadmap - Lighter weight than /gad:pause-work — no phase state, no plan context - The value is in Context and Next Steps — a cold-start session can pick up immediately - Threads can be promoted to phases or backlog items when they mature: /gad:add-phase or /gad:add-backlog with context from the thread - Thread files live in .planning/threads/ — no collision with phases or other GAD structures