gsd-workstreams

Track and switch between parallel development workstreams across local git repositories.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/nnexai/git-stacks --skill gsd-workstreams-nnexai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-workstreams
Source: https://github.com/nnexai/git-stacks/tree/main/.codex/skills/gsd-workstreams
Command: npx skills add https://github.com/nnexai/git-stacks --skill gsd-workstreams-nnexai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the challenge of managing multiple concurrent development tasks or tickets by providing a structured way to isolate, track, and switch between different workstreams without losing context.

Core Features & Use Cases

  • Workstream Lifecycle Management: Create, resume, and complete tasks while maintaining clear status tracking for each.
  • Context Switching: Quickly switch between active workstreams to maintain focus during multi-tasking.
  • Use Case: A developer working on three different feature tickets simultaneously can use this skill to isolate each task's progress and switch between them instantly without manual directory or branch management.

Quick Start

Use the gsd-workstreams skill to create a new workstream named feature-login-flow.

Frequently Asked Questions about gsd-workstreams

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

FAQPage Schema
How do I manage multiple parallel development workstreams without losing context?

You can manage parallel development workstreams by using structured lifecycle tracking to isolate, track, and switch between concurrent tasks. This maintains context for each ticket, allowing instant switching between active workstreams without manual directory or branch management.

How does context switching work when juggling multiple git feature branches?

Context switching across git feature branches works by resuming active workstreams through session-local persistence. It instantly isolates each task's progress and coordinates milestone-based tasks without requiring manual directory or branch management.

Do I need gsd-core tools to track milestone-based task lifecycles?

Yes, gsd-core tools are required to execute state transitions for milestone-based task lifecycles. The workstream management relies on this integration to coordinate tasks and persist session-local workstream states across local git repositories.

Can I coordinate milestone-based tasks across local git repositories?

Yes, you can coordinate milestone-based tasks across local git repositories and project directories. The system operates across these directories to provide lifecycle tracking and status reporting for parallel development workstreams.

What is the best way to isolate concurrent development tickets for status reporting?

The best way to isolate concurrent development tickets is using structured workstream lifecycle management. This provides clear status tracking for each task, allowing you to create, resume, and complete tasks while maintaining isolated progress reporting.