skills.rest
ArtRiv
ArtRivCOMMUNITY
Explore all skills by this author →
GitHub

gsd-thread

List, resume, and create persistent context threads in .planning/threads.

Updated Feb 11, 2026
Search Tags:#workflow#debugging#documentation#knowledge management#threads#context persistence
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-thread-artriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-thread
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-thread-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of losing momentum between sessions when you need to carry ongoing investigation notes, decisions, and next actions forward.

Core Features & Use Cases

  • Thread listing and discovery: Quickly see all existing threads and their statuses to resume work confidently.
  • Resume persistent context: Load a specific thread’s stored context into the current session and continue from where you left off.
  • Thread creation from new intent: Turn a new description into a durable, slugged thread with placeholders for goal, context, references, and next steps, then optionally populate it from the current conversation.
  • Use Case: When debugging a recurring issue, create a thread for the investigation, capture findings as they evolve, and resume the same thread later without rebuilding context.

Quick Start

Resume an existing investigation thread by running: /gsd-thread perf-investigation.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I keep cross-session context for ongoing debugging investigations?▼

Cross-session context persistence stores investigation notes, decisions, and next actions in thread files, allowing you to resume ongoing debugging work without rebuilding context between sessions.

What is the best way to manage persistent workflow threads across sessions?▼

Persistent workflow threads are managed by creating slugged files that store goal, context, references, and next steps, enabling you to list, resume, and update statuses for ongoing work.

How do I resume a specific thread by name after closing my session?▼

Resuming a specific thread by name loads its stored context into the current session and automatically updates the thread status from OPEN to IN PROGRESS for continuous actionability.

Can I create a new context thread from a fresh text description?▼

Creating a new context thread from a description generates a durable, slugged thread file with placeholders for goal and context, which can be populated from the current conversation.

Where are persistent context threads stored on disk?▼

Persistent context threads are stored as files within the .planning/threads directory, enabling reading and writing operations to preserve knowledge management state across sessions.

When do I need persistent context threads for software engineering workflows?▼

Persistent context threads are needed when investigating recurring issues or managing complex workflows, ensuring evolving findings and action items are captured durably rather than lost between sessions.

Related Skills

Explore More Software Engineering Skills→
zerAdazerAda

gsd-thread

Create, list, and resume persistent text-file threads for cross-session tasks.

Community
Intermediate
jiahao-shao1jiahao-shao1
36

handoff

Generate a structured handoff summary from conversation, git diff, and task list.

Community
Intermediate
TruCol270TruCol270
1

gsd-thread

Create, list, and resume file-based context threads under .planning/threads.

Community
Intermediate
wilsonfaustinowilsonfaustino
2

wrap-up

Automate end-of-session knowledge capture with Obsidian notes and memory updates.

Community
Intermediate