gsd-thread - SKILL.md Agent Skill

name: gsd-thread description: "Manage persistent context threads for cross-session work"

## A. Skill Invocation - This skill is invoked when the user mentions `gsd-thread` or describes a task matching this skill. - Treat all user text after the skill mention as `{{GSD_ARGS}}`. - If no arguments are present, treat `{{GSD_ARGS}}` as empty.

B. User Prompting

When the workflow needs user input, prompt the user conversationally:

Present options as a numbered list in your response text
Ask the user to reply with their choice
For multi-select, ask for comma-separated numbers

C. Tool Usage

Use these Windsurf tools when executing GSD workflows:

Shell for running commands (terminal operations)
StrReplace for editing existing files
Read, Write, Glob, Grep, Task, WebSearch, WebFetch, TodoWrite as needed

D. Subagent Spawning

When the workflow needs to spawn a subagent:

Use Task(subagent_type="generalPurpose", ...)
The model parameter maps to Windsurf's model options (e.g., "fast")

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 {{GSD_ARGS}} to determine mode:

**If no arguments or {{GSD_ARGS}} 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: /gsd-thread <description>

**If {{GSD_ARGS}} 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 {{GSD_ARGS}} is a new description (no matching thread file):**

Create a new thread:

Generate slug from description:

SLUG=$(node "/Users/diegocaminor/Documents/proyectos/anyone-ai/final-project/anyone-ai-interviewer-frontend/.windsurf/get-shit-done/bin/gsd-tools.cjs" generate-slug "{{GSD_ARGS}}")

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:

node "/Users/diegocaminor/Documents/proyectos/anyone-ai/final-project/anyone-ai-interviewer-frontend/.windsurf/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"

Report:

## 🧵 Thread Created

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

Resume anytime with: /gsd-thread {slug}

- Threads are NOT phase-scoped — they exist independently of the roadmap - Lighter weight than /gsd-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: /gsd-add-phase or /gsd-add-backlog with context from the thread - Thread files live in .planning/threads/ — no collision with phases or other GSD structures