qsd-thread

Create, list, or resume persistent context threads across Claude sessions.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/thecomputer07/qsd --skill qsd-thread
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qsd-thread
Source: https://github.com/thecomputer07/qsd/tree/main/skills/qsd-thread
Command: npx skills add https://github.com/thecomputer07/qsd --skill qsd-thread

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-session work often loses context between conversations. This skill provides lightweight, persistent context threads to capture goals, notes, and references so work can resume seamlessly.

Core Features & Use Cases

  • Create, list, and resume lightweight context threads that persist across Claude sessions.
  • Each thread is a self-contained context blob with a slug, status, and built-in references.
  • Use cases include long-running investigations, handoffs between agents, and ongoing research tasks.

Quick Start

Describe a new thread to create it and begin tracking its context.

Frequently Asked Questions about qsd-thread

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

FAQPage Schema
How do I persist context across multiple Claude sessions?

To persist context across multiple Claude sessions, create lightweight context threads using a .planning/threads directory with slug-based filenames. Each thread stores goals, notes, and references in a simple YAML body, ensuring work resumes seamlessly across sessions.

What is the best way to manage cross-session workflow handoffs?

The best way to manage cross-session workflow handoffs is by creating persistent context threads that capture goals and references. These threads maintain status transitions to track progress, allowing different agents or sessions to pick up work without losing context.

How do I create and resume persistent context threads for ongoing research?

To create and resume persistent context threads for ongoing research, describe a new thread to start tracking its context, then use list and resume commands to access existing threads. Each thread uses YAML format and status transitions to manage progress across sessions.

Do I need any specific dependencies to track cross-session planning context?

No specific dependencies are required to track cross-session planning context. The system uses a simple directory structure with slug-based filenames and YAML bodies to store thread information, making it lightweight and accessible without external tools.

When should I use persistent context threads for my workflow?

Use persistent context threads for long-running investigations, agent handoffs, and ongoing research tasks. These threads keep goals and notes cohesive and accessible across multiple Claude sessions, preventing context loss between conversations.

How does status transition work for context threads?

Status transitions for context threads work by updating a status field within the YAML body of each thread file. This mechanism tracks progress through different stages, allowing users to manage and monitor the advancement of cross-session work.