d4767ac2e0
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2.2 KiB
name, description, allowed-tools
| name | description | allowed-tools | ||
|---|---|---|---|---|
| gsd:workstreams | Manage parallel workstreams — list, create, switch, status, progress, complete, and resume |
|
/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 "$GSD_TOOLS" workstream list --raw --cwd "$CWD"
Display the workstreams in a table format showing name, status, current phase, and progress.
create
Run: node "$GSD_TOOLS" 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 "$GSD_TOOLS" workstream status <name> --raw --cwd "$CWD"
Display detailed phase breakdown and state information.
switch
Run: node "$GSD_TOOLS" 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 "$GSD_TOOLS" workstream progress --raw --cwd "$CWD"
Display a progress overview across all workstreams.
complete
Run: node "$GSD_TOOLS" 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.