create-rule
Create Cursor rules for persistent AI guidance. Use when the user wants to create a rule, add coding standards, set up project…
@coco-researchInstall SkillDevelopment
Skill
/gsd-workstreams
Use when the user runs /gsd-workstreams or asks to list, create, switch, status, progress, complete, or resume parallel workstreams for concurrent milestone work. The active one is tracked in the GSD_WS variable.
Claude Code
$ npx -y skills add coco-research/coco --skill gsd-workstreams --agent claude-code
Codex
$ npx skills add coco-research/coco --skill gsd-workstreams -a codex -y
Cursor
$ npx skills add coco-research/coco --skill gsd-workstreams -a cursor -y
Gemini CLI
$ npx skills add coco-research/coco --skill gsd-workstreams -a gemini-cli -y
GitHub Copilot
$ npx skills add coco-research/coco --skill gsd-workstreams -a github-copilot -y
OpenCode
$ npx skills add coco-research/coco --skill gsd-workstreams -a opencode -y
Windsurf
$ npx skills add coco-research/coco --skill gsd-workstreams -a windsurf -y
SKILL.md
gsd-workstreams.SKILL.mdname: gsd-workstreams
description: "Use when the user runs /gsd-workstreams or asks to list, create, switch, status, progress, complete, or resume parallel workstreams for concurrent milestone work. The active one is tracked in the GSD_WS variable."
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_WS` 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: "Use when the user runs /gsd-workstreams or asks to list, create, switch, status, progress, complete, or resume parallel workstreams for concurrent milestone work. The active one is tracked in the GSD_WS variable." 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_WS` 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.
Ships withcoco
495 personas across 13 departments, 229 skills[^installed] and 388 commands in the full catalog (coco 1.9.0, 2026-10-21). Agent skills, slash commands and subagents for Claude Code, Cursor, Codex and other AI coding agents.
631200 skills53 agents
Stars on GitHub
Momentum
- stars in total
- 631
Other skills on coco.
@coco-researchInstall Skillcreate-skill
Guides users through creating effective Agent Skills for Cursor. Use when the user wants to create, write, or author a new skill,…
@coco-researchInstall Skillcreate-subagent
Create custom subagents for specialized AI tasks. Use when the user wants to create a new type of subagent, set up task-specific…
@coco-researchInstall Skillmigrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills…
@coco-researchInstall Skillupdate-cursor-settings
Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences,…
@coco-researchInstall Skillagent-lightning
Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent…
@coco-researchInstall SkillMore skills from other plugins.
Auto-invoked
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
@obraInstall Skillask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
@mattpocockInstall SkillAuto-invoked
Questions about gsd-workstreams.
- Which coding agents can use gsd-workstreams?
- gsd-workstreams installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.