73c1af5168
Commands are now installed as commands/gsd/<name>.md and invoked as /gsd:<name> in Claude Code. The old hyphen form /gsd-<name> was still hardcoded in hundreds of places across workflows, references, templates, lib modules, and command files — causing "Unknown command" errors whenever GSD suggested a command to the user. Replace all /gsd-<cmd> occurrences where <cmd> is a known command name (derived at runtime from commands/gsd/*.md) using a targeted Node.js script. Agent names, tool names (gsd-sdk, gsd-tools), directory names, and path fragments are not touched. Adds regression test tests/bug-2543-gsd-slash-namespace.test.cjs that enforces zero legacy occurrences going forward. Removes inverted tests/stale-colon-refs.test.cjs (bug #1748) which enforced the now-obsolete hyphen form; the new bug-2543 test supersedes it. Updates 5 assertion tests that hardcoded the old hyphen form to accept the new colon form. Closes #2543 Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
70 lines
2.1 KiB
Markdown
70 lines
2.1 KiB
Markdown
---
|
|
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: `gsd-sdk query workstream.list --raw --cwd "$CWD"`
|
|
Display the workstreams in a table format showing name, status, current phase, and progress.
|
|
|
|
### create
|
|
Run: `gsd-sdk query 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: `gsd-sdk query workstream.status <name> --raw --cwd "$CWD"`
|
|
Display detailed phase breakdown and state information.
|
|
|
|
### switch
|
|
Run: `gsd-sdk query 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: `gsd-sdk query workstream.progress --raw --cwd "$CWD"`
|
|
Display a progress overview across all workstreams.
|
|
|
|
### complete
|
|
Run: `gsd-sdk query 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-sdk query into a human-readable display.
|
|
Include the `${GSD_WS}` flag in any routing suggestions.
|