skills.rest
coco-research
coco-researchCOMMUNITY
Explore all skills by this author →
GitHub

gsd-thread

Create, list, and resume filesystem-backed context threads with status tracking.

264|11|Updated Apr 25, 2026
Search Tags:#context management#session continuity#filesystem#task tracking#workflow organization#persistent threads
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-thread-coco-research
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-thread
Command: npx skills add https://github.com/coco-research/coco --skill gsd-thread-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps long-running work organized when a task spans multiple sessions, so you do not lose context between conversations.

Core Features & Use Cases

  • Create Persistent Threads: Start a lightweight thread file for an investigation, feature idea, bug fix, or follow-up task.
  • List and Resume Work: Review existing threads, reopen a specific thread by name, and continue from the stored context.
  • Track Status and Next Steps: Maintain thread status, references, and immediate next actions so future sessions can pick up quickly.

Quick Start

Ask the skill to create a thread for your ongoing task, or to list and resume an existing thread by name.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I maintain context across coding sessions for an ongoing investigation?▼

Persistent context threads store your investigation status, references, and next steps in filesystem-backed files, allowing future sessions to resume work quickly without losing context between conversations.

How do I list and resume a specific task thread from a previous session?▼

You can list existing threads to review ongoing tasks and reopen a specific thread by name, which restores the stored context so you can continue your follow-up tasks immediately.

When do I need persistent threads for workflow organization?▼

Persistent threads are needed when a task spans multiple sessions, such as long-running bug fixes or feature development, ensuring your workflow organization and progress survive beyond a single conversation.

Can I track status and next steps for cross-session work without external databases?▼

Yes, this approach uses filesystem-backed thread files with automatic slug generation to track status and next steps, eliminating the need for external databases to keep cross-session work organized.

What is the best way to recover context for a bug fix started in a previous session?▼

The best way to recover context for a bug fix is to create a lightweight thread file that maintains the thread status and immediate next actions, enabling quick context recovery for ongoing investigations.

Related Skills

Explore More Software Engineering Skills→
zerAdazerAda

gsd-thread

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

Community
Intermediate
tiweentiween

bmad-quick-dev

Automate code development workflows from planning through review using predefined templates.

Official
Advanced
lengo0951lengo0951

ck:project-management

Manages tasks, updates plans, triggers documentation changes, and generates project status reports.

Community
Advanced
mozumasumozumasu
139

markdown-session-format

Standardize Claude Code session logs into a consistent Markdown format.

Community
Basic