gsd-thread

Create, list, close, or resume persistent context threads under .planning/threads.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-thread-poom5741
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-thread
Source: https://github.com/Poom5741/eggo-world-pb/tree/main/.qwen/skills/gsd-thread
Command: npx skills add https://github.com/Poom5741/eggo-world-pb --skill gsd-thread-poom5741

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage persistent context threads that span multiple sessions but don't belong to any single phase, providing a lightweight memory for ongoing work.

Core Features & Use Cases

  • Create, list, close, or resume persistent context threads to organize cross-session knowledge.
  • Store goals, decisions, and next steps in easily accessible threads that you can resume later.
  • Promote threads to phases or backlog items when they mature, enabling flexible workflows.

Quick Start

Create or resume a persistent context thread by providing a description.

Frequently Asked Questions about gsd-thread

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

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

To persist context across sessions, you can create persistent context threads that store goals, decisions, and next steps as lightweight cross-session knowledge stores.

What is the best way to manage cross-session notes without a formal project phase?

Cross-session notes are managed as persistent context threads, providing lightweight memory for ongoing work that spans multiple sessions but does not belong to any specific phase.

Can I resume a persistent context thread after closing it?

Yes, you can resume persistent context threads by parsing arguments to determine the mode, allowing you to pick up goals and decisions exactly where you left off.

How do I promote cross-session threads into structured backlog items?

You can promote mature persistent context threads into phases or backlog items, enabling flexible workflows as the stored decisions and next steps evolve.

How does markdown frontmatter context storage work for thread management?

Markdown frontmatter context storage works by reading and updating frontmatter within thread files located under the .planning/threads directory to maintain sanitized slugs and metadata.

Do I need any external dependencies to manage persistent context threads?

No external dependencies are required to manage persistent context threads, as the system parses arguments, sanitizes slugs, and manages thread files internally.