gsd-thread

Create, list, resume, and close persistent context threads by slug.

1|Updated Sep 6, 2015

Search Tags:#workflow management #persistent memory #knowledge store #context threads #slug-based routing #cross-session work #CLI assistant

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-thread-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-thread
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-thread-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents you from losing important context between sessions by giving you a place to store ongoing, cross-phase knowledge as persistent threads.

Core Features & Use Cases

Create and manage threads: Start new persistent context threads for work that spans multiple sessions.
Resume and close by slug: Reopen or complete a thread using a stable identifier so you can pick up where you left off.
Scope fit: Use it for persistent work that does not belong to a single project phase or one-off task.

Quick Start

Create a new thread for your ongoing research by telling the assistant to open a fresh gsd-thread and set it up for future cross-session continuation.

Frequently Asked Questions about gsd-thread

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep persistent context for cross-session work in a CLI assistant?▼

Persistent context threads store ongoing cross-phase knowledge so cross-session work retains important information. Threads are managed via deterministic lifecycle operations with read and write access to a configured markdown path.

What is the best way to resume a workflow task across independent sessions?▼

Resume cross-session work by reopening a thread using its stable slug identifier. Slug-based routing allows you to pick up exactly where you left off across independent sessions and tasks without losing prior context.

When do I need persistent context threads for my workflow management?▼

Persistent context threads are needed for ongoing work that spans multiple sessions and does not belong to a single project phase. They prevent the loss of important cross-phase knowledge when transitioning between independent tasks.

How do I create and close a knowledge store thread using a slug?▼

Create a new thread to start storing persistent context, and close it by applying deterministic lifecycle operations using its slug. This ensures stable identification throughout the thread lifecycle from creation to completion.

Can I list active context threads to find my ongoing cross-session tasks?▼

Yes, listing active context threads is supported. You can list all persistent threads managed by the workflow system to locate and identify ongoing cross-session tasks by their slugs for easy retrieval.

Do I need a specific markdown path configured to use persistent context threads?▼

Yes, a configured workflow thread markdown path is required. The Skill needs read and write access to this designated path to execute deterministic thread lifecycle operations and store the persistent knowledge.