/gsd-workstreams
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
$ npx -y skills add coco-research/coco --skill gsd-workstreams --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/gsd-workstreams
Context preview
The summary Claude sees to decide when to auto-load this skill.
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
SKILL.md
gsd-workstreams.SKILL.mdname: gsd-workstreams
description: "Manage parallel workstreams — list, create, switch, status, progress, complete, and resume"
allowed-tools:
- Read
- Bash
/gsd-workstreams
Manage parallel workstreams for concurrent milestone work.
Usage
`/gsd-workstreams [subcommand] [args]`
Subcommands
| Command | Description | |---------|-------------| | `list` | List all workstreams with status | | `create <name>` | Create a new workstream | | `status <name>` | Detailed status for one workstream | | `switch <name>` | Set active workstream | | `progress` | Progress summary across all workstreams | | `complete <name>` | Archive a completed workstream | | `resume <name>` | Resume work in a workstream |
Step 1: Parse Subcommand
Parse the user's input to determine which workstream operation to perform. If no subcommand given, default to `list`.
Step 2: Execute Operation
list
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream list --raw --cwd "$CWD"` Display the workstreams in a table format showing name, status, current phase, and progress.
create
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream create <name> --raw --cwd "$CWD"` After creation, display the new workstream path and suggest next steps:
- `/gsd-new-milestone --ws <name>` to set up the milestone
status
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream status <name> --raw --cwd "$CWD"` Display detailed phase breakdown and state information.
switch
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream set <name> --raw --cwd "$CWD"` Also set `GSD_WORKSTREAM` for the current session when the runtime supports it. If the runtime exposes a session identifier, GSD also stores the active workstream session-locally so concurrent sessions do not overwrite each other.
progress
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream progress --raw --cwd "$CWD"` Display a progress overview across all workstreams.
complete
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream complete <name> --raw --cwd "$CWD"` Archive the workstream to milestones/.
resume
Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
Step 3: Display Results
Format the JSON output from gsd-tools into a human-readable display. Include the `${GSD_WS}` flag in any routing suggestions.
Read more
name: gsd-workstreams description: "Manage parallel workstreams — list, create, switch, status, progress, complete, and resume" allowed-tools: - Read - Bash
/gsd-workstreams
Manage parallel workstreams for concurrent milestone work.
Usage
`/gsd-workstreams [subcommand] [args]`
Subcommands
| Command | Description | |---------|-------------| | `list` | List all workstreams with status | | `create <name>` | Create a new workstream | | `status <name>` | Detailed status for one workstream | | `switch <name>` | Set active workstream | | `progress` | Progress summary across all workstreams | | `complete <name>` | Archive a completed workstream | | `resume <name>` | Resume work in a workstream |
Step 1: Parse Subcommand
Parse the user's input to determine which workstream operation to perform. If no subcommand given, default to `list`.
Step 2: Execute Operation
list
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream list --raw --cwd "$CWD"` Display the workstreams in a table format showing name, status, current phase, and progress.
create
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream create <name> --raw --cwd "$CWD"` After creation, display the new workstream path and suggest next steps:
- `/gsd-new-milestone --ws <name>` to set up the milestone
status
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream status <name> --raw --cwd "$CWD"` Display detailed phase breakdown and state information.
switch
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream set <name> --raw --cwd "$CWD"` Also set `GSD_WORKSTREAM` for the current session when the runtime supports it. If the runtime exposes a session identifier, GSD also stores the active workstream session-locally so concurrent sessions do not overwrite each other.
progress
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream progress --raw --cwd "$CWD"` Display a progress overview across all workstreams.
complete
Run: `node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" workstream complete <name> --raw --cwd "$CWD"` Archive the workstream to milestones/.
resume
Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
Step 3: Display Results
Format the JSON output from gsd-tools into a human-readable display. Include the `${GSD_WS}` flag in any routing suggestions.
Meet Coco. A superintelligent agent framework powered by an advisory board of 389 world-class minds. Scale your AI assistant into a complete engineering department with 142 skills, 277 commands, and persistent state. Universal compatibility. Local privacy. Free and open source.
Repo: coco-research/coco
Other skills on coco.
- /create-rule
Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project conventions, configure file-specific patterns, create RULE.md files, or asks about .cursor/rules/ or AGENTS.md.
Open skill - /create-skill
Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill, or asks about skill structure, best practices, or SKILL.md format.
Open skill - /create-subagent
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific agents, configure code reviewers, debuggers, or domain-specific assistants with custom prompts.
Open skill - /migrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use when the user wants to migrate rules or commands to skills, convert .mdc rules to SKILL.md format, or consolidate commands
Open skill - /update-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.
Open skill - /agent-lightning
Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent training, instrumenting agents with tracing, configuring LightningStore, implementing reward functions, or optimizing prompts with RL/APO algorithms.
Open skill