All command files use @./.claude/ relative paths — break when CWD ≠ $HOME

[Nicopatron]

GSD Version

1.22.4

Runtime

Claude Code

What happened?

All 32 command files in commands/gsd/ reference workflows using relative paths like:

@./.claude/get-shit-done/workflows/pause-work.md

When working from a project directory (e.g., ~/Documents/my-project/), Claude Code resolves ./ relative to CWD, not relative to $HOME. This means it looks for:

~/Documents/my-project/.claude/get-shit-done/workflows/pause-work.md

...which doesn't exist. Claude then says "The GSD workflow file doesn't exist" and improvises instead of following the workflow.

Scope

This affects every GSD command, not just one. A quick grep shows all 32 files use the same @./.claude/get-shit-done/ pattern with zero files using absolute or $HOME-based paths.

# All use relative
grep -rl '@\./\.claude/get-shit-done/' ~/.claude/commands/gsd/ | wc -l
# 32

# None use absolute
grep -rl '@~/\|@\$HOME\|@/Users/' ~/.claude/commands/gsd/ | wc -l
# 0

What did you expect?

Commands should work regardless of CWD. The @ file references should resolve to the actual GSD installation directory.

Suggested fix

Replace @./.claude/get-shit-done/ with an absolute or home-relative path that Claude Code can resolve from any directory. If Claude Code supports ~ in @ references, @~/.claude/get-shit-done/ would work. Otherwise, the installer could template the absolute path at install time.

Workaround

From $HOME, commands work fine since ./ resolves to ~/. The issue only manifests when the shell CWD is a project directory.

Steps to reproduce

1. cd ~/Documents/any-project/ (any dir that isn't $HOME)
2. Run /gsd:pause-work (or any /gsd: command)
3. Claude says the workflow file doesn't exist

Relevant logs or error messages

Claude: "The GSD workflow file doesn't exist at ./.claude/get-shit-done/workflows/pause-work.md"