OpenParable
Skip to content
← Back to skills

Gsd Thread

Productivity
gsd-thread

Gsd Thread is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Manage persistent context threads for cross-session work

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/context-management/gsd-thread/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/gsd-thread-3de4e87c, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Parse $ARGUMENTS to determine mode:

<mode_list> 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: /gsd-thread <description>

</mode_list>

<mode_resume> 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. </mode_resume>

<mode_create> If $ARGUMENTS is a new description (no matching thread file):

Create a new thread:

  1. Generate slug from description:

    SLUG=$(node "$GSD_TOOLS" generate-slug "$ARGUMENTS" --raw)
    
  2. Create the threads directory if needed:

    mkdir -p .planning/threads
    
  3. 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
    
  4. If there's relevant context in the current conversation (code snippets, error messages, investigation results), extract and add it to the Context section.

  5. Commit:

    node "$GSD_TOOLS" commit "docs: create thread — ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
    
  6. Report:

    ## 🧵 Thread Created
    
    Thread: {slug}
    File: .planning/threads/{slug}.md
    
    Resume anytime with: /gsd-thread {slug}
    

</mode_create>