gsd-workstreams

Organizes parallel engineering workstreams by milestone using the gtd-tools CLI with session-aware routing and isolation.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-workstreams-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-workstreams
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-workstreams
Command: npx skills add https://github.com/coco-research/coco --skill gsd-workstreams-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage multiple concurrent engineering workstreams without losing track of status, ownership, or the next action to take.

Core Features & Use Cases

  • Workstream lifecycle management: List, create, switch, inspect, progress, complete, and resume workstreams from a single interface.
  • Concurrent milestone coordination: Keep parallel streams organized while moving between active efforts and archived work.
  • Use Case: A developer juggling feature work, bug fixes, and release prep can keep each effort in its own workstream and quickly return to the right context.

Quick Start

Ask the assistant to show your current workstreams and switch you to the one you want to continue.

Frequently Asked Questions about gsd-workstreams

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

FAQPage Schema
How do I manage parallel workstreams during concurrent software engineering?

Managing parallel workstreams involves organizing concurrent development tasks by milestone, allowing you to list, create, switch, and resume isolated sessions to track progress without losing context.

What is session-local active-workstream state for CLI automation?

Session-local active-workstream state is an isolation mechanism that uses workspace-aware routing to keep concurrent CLI automation tasks separated, ensuring parallel sessions do not overwrite each other's progress.

How do I switch between active workstreams and track milestone progress?

Switching workstreams and tracking milestone progress requires a single interface to inspect status, update progress, and resume concurrent development tasks, keeping parallel efforts organized during context switching.

Can I use this for concurrent milestone coordination with feature work and bug fixes?

Yes, concurrent milestone coordination is supported for developers juggling feature work, bug fixes, and release prep, keeping each effort in its own workstream to quickly return to the right context.

Does this workstream tracking require external dependencies?

No external dependencies are required for workstream tracking, as it uses the gsd-tools CLI with workspace-aware routing directly to manage the lifecycle of concurrent development tasks.

Why use isolated workstreams for concurrent development tasks?

Isolated workstreams prevent status, ownership, and next-action loss during concurrent development, keeping parallel milestone-based engineering efforts separated within their own tracked sessions.