gsd-thread

Create, list, and resume persistent context threads stored as Markdown files.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-thread-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-thread
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-thread-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work that spans multiple sessions but doesn't belong to a specific project phase often loses context between conversations. This Skill maintains lightweight persistent threads in .planning/threads/ so a cold-start session can pick up exactly where the last one left off. ## Core Features & Use Cases - Thread Listing: Run without arguments to see all threads with their status (OPEN, IN PROGRESS, RESOLVED) and last-updated dates. - Thread Resume: Pass an existing thread name to load its full context into the current session and continue working. - Thread Creation: Pass a new description to generate a slug, write a structured Markdown thread file with Goal, Context, References, and Next Steps sections, and commit it to the repository. - Use Case: You spent a session investigating a TCP timeout bug but haven't fixed it. Create a thread capturing the error messages and findings, then resume it days later with full context intact. ## Quick Start Ask the assistant to create a thread describing your current investigation, for example by saying: create a thread for the pasta TCP timeout investigation.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I create a persistent context thread for cross-session work?▼

Invoke the skill with a description of the work, such as a bug investigation topic. It generates a slug, writes a structured Markdown file to .planning/threads/ with Goal, Context, and Next Steps sections, and commits it to the repository.

How do I resume work from a previous session thread?▼

Pass the existing thread name as the argument. The skill reads the thread file from .planning/threads/, displays its full context, and updates the status to IN PROGRESS if it was OPEN.

Where are thread files stored and what format do they use?▼

Threads are stored as Markdown files in the .planning/threads/ directory. Each file contains a title, status field, goal, context notes, references, and next steps for the following session.

What is the difference between a thread and a project phase?▼

Threads are lightweight, phase-independent knowledge stores with no plan or roadmap state. They suit exploratory work, and mature threads can be promoted to phases or backlog items later.

What happens if no threads exist when I list them?▼

The skill reports that no threads were found and suggests creating one by providing a description. The .planning/threads/ directory is created automatically on first use.