Skill
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…
@coco-researchView 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.
Install
$ 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.
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.
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
CoCo Super Intelligence is the orchestration layer that turns Claude Code, Cursor, or Codex into an engineering department: a routed advisory board, 226 skills, 386 commands, persistent state. Local. Open-core — MIT core; Super Intelligence is proprietary, own-use.
Get the whole plugin
Stats
287
Stars
12
Forks
Active
Maintenance
HTML
Language
4d ago
Last commit
4mo ago
Created
Repo: coco-research/coco
Other skills on coco.
@coco-researchView SkillSkill
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…
@coco-researchView SkillSkill
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…
@coco-researchView SkillSkill
migrate-to-skills
Convert 'Applied intelligently' Cursor rules (.cursor/rules/*.mdc) and slash commands (.cursor/commands/*.md) to Agent Skills format (.cursor/skills/). Use…
@coco-researchView SkillSkill
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…
@coco-researchView SkillSkill
agent-lightning
Train and optimize AI agents using Microsoft's Agent Lightning framework with reinforcement learning. Use when setting up agent training, instrumenting agents…
@coco-researchView Skill