skills.rest
lgwanai
lgwanaiCOMMUNITY
Explore all skills by this author →
GitHub

gsd-thread

Create, list, resume, and close named persistent context threads.

4|1|Updated Mar 22, 2026
Search Tags:#workflow continuity#persistent context#session resume#cross-session#thread management#slug-based#knowledge storage
One-click install
npx skills add https://github.com/lgwanai/openforce --skill gsd-thread-lgwanai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/lgwanai/openforce/tree/main/skills/gsd-thread
Command: npx skills add https://github.com/lgwanai/openforce --skill gsd-thread-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you preserve important work context across multiple sessions so you can continue planning, analysis, and execution without losing prior decisions or discoveries.

Core Features & Use Cases

  • Create and manage persistent threads: Start new cross-session context stores, resume existing ones, and keep them organized by slug.
  • List and inspect thread state: Review available threads and their resolution status to avoid duplicating effort.
  • Close threads when work is done: Mark a thread as finished so future work stays focused on what is still active.

Quick Start

Create a new context thread to store your cross-session findings with the slug "security-notes" so you can resume it later.

Frequently Asked Questions about gsd-thread

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

FAQPage Schema
How do I maintain persistent context for cross-session project work?▼

You maintain persistent context for cross-session work by creating named threads that store knowledge across project phases. This allows you to resume planning and execution later without losing prior decisions or discoveries.

What is the best way to organize session resume points for multi-phase workflows?▼

Organizing session resume points with slug-based navigation lets you list, inspect, and resume specific context threads. This ensures multi-session projects remain independent of any single workflow stage while avoiding duplicated effort.

How do I close persistent context threads when a project phase is finished?▼

You close persistent context threads by marking their resolution status as finished. This keeps future work focused strictly on active threads and prevents completed knowledge stores from cluttering ongoing multi-session execution.

Does cross-session thread management require heavy external dependencies?▼

Cross-session thread management requires only lightweight thread storage for read and write operations. It applies to multi-session projects needing knowledge persistence without introducing complex external dependencies or workflow stage constraints.

When do I need slug-based thread management for my workflow continuity?▼

You need slug-based thread management when a project requires workflow continuity across multiple sessions. It provides persistent knowledge storage and lifecycle operations so you can resume named threads exactly where prior analysis left off.

Related Skills

Explore More Software Engineering Skills→
aoecosystemaoecosystem

build-scope-of-work

Generate a phase-structured Scope of Work HTML from an approved Project Brief.

Official
Advanced
onelee85onelee85

gsd-thread

Create, list, or resume persistent context threads with slug-based storage.

Community
Intermediate
diegocanepadiegocanepa

vcs-issue-management

Manage issue lifecycles across GitHub and GitLab with comments, states, and assignments.

Community
Intermediate
em-jonesem-jones
1

Agent Context Management and Handoff

Log agent work progress, decisions, and blockers via the td CLI.

Community
Advanced