mirror of
https://github.com/glittercowboy/get-shit-done
synced 2026-04-25 17:25:23 +02:00
fix: replace /gsd: slash command format with /gsd- skill format in all user-facing content (#1579)
* 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>
This commit is contained in:
Quang Do
174
README.md
174
README.md
@@ -96,7 +96,7 @@ The installer prompts you to choose:
|
||||
2. **Location** — Global (all projects) or local (current project only)
|
||||
|
||||
Verify with:
|
||||
- Claude Code / Gemini / Copilot / Antigravity: `/gsd:help`
|
||||
- Claude Code / Gemini / Copilot / Antigravity: `/gsd-help`
|
||||
- OpenCode / Kilo / Augment: `/gsd-help`
|
||||
- Codex: `$gsd-help`
|
||||
|
||||
@@ -229,12 +229,12 @@ If you prefer not to use that flag, add this to your project's `.claude/settings
|
||||
|
||||
## How It Works
|
||||
|
||||
> **Already have code?** Run `/gsd:map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `/gsd:new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.
|
||||
> **Already have code?** Run `/gsd-map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `/gsd-new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.
|
||||
|
||||
### 1. Initialize Project
|
||||
|
||||
```
|
||||
/gsd:new-project
|
||||
/gsd-new-project
|
||||
```
|
||||
|
||||
One command, one flow. The system:
|
||||
@@ -253,7 +253,7 @@ You approve the roadmap. Now you're ready to build.
|
||||
### 2. Discuss Phase
|
||||
|
||||
```
|
||||
/gsd:discuss-phase 1
|
||||
/gsd-discuss-phase 1
|
||||
```
|
||||
|
||||
**This is where you shape the implementation.**
|
||||
@@ -276,14 +276,14 @@ The deeper you go here, the more the system builds what you actually want. Skip
|
||||
|
||||
**Creates:** `{phase_num}-CONTEXT.md`
|
||||
|
||||
> **Assumptions Mode:** Prefer codebase analysis over questions? Set `workflow.discuss_mode` to `assumptions` in `/gsd:settings`. The system reads your code, surfaces what it would do and why, and only asks you to correct what's wrong. See [Discuss Mode](docs/workflow-discuss-mode.md).
|
||||
> **Assumptions Mode:** Prefer codebase analysis over questions? Set `workflow.discuss_mode` to `assumptions` in `/gsd-settings`. The system reads your code, surfaces what it would do and why, and only asks you to correct what's wrong. See [Discuss Mode](docs/workflow-discuss-mode.md).
|
||||
|
||||
---
|
||||
|
||||
### 3. Plan Phase
|
||||
|
||||
```
|
||||
/gsd:plan-phase 1
|
||||
/gsd-plan-phase 1
|
||||
```
|
||||
|
||||
The system:
|
||||
@@ -301,7 +301,7 @@ Each plan is small enough to execute in a fresh context window. No degradation,
|
||||
### 4. Execute Phase
|
||||
|
||||
```
|
||||
/gsd:execute-phase 1
|
||||
/gsd-execute-phase 1
|
||||
```
|
||||
|
||||
The system:
|
||||
@@ -352,7 +352,7 @@ This is why "vertical slices" (Plan 01: User feature end-to-end) parallelize bet
|
||||
### 5. Verify Work
|
||||
|
||||
```
|
||||
/gsd:verify-work 1
|
||||
/gsd-verify-work 1
|
||||
```
|
||||
|
||||
**This is where you confirm it actually works.**
|
||||
@@ -366,7 +366,7 @@ The system:
|
||||
3. **Diagnoses failures automatically** — Spawns debug agents to find root causes
|
||||
4. **Creates verified fix plans** — Ready for immediate re-execution
|
||||
|
||||
If everything passes, you move on. If something's broken, you don't manually debug — you just run `/gsd:execute-phase` again with the fix plans it created.
|
||||
If everything passes, you move on. If something's broken, you don't manually debug — you just run `/gsd-execute-phase` again with the fix plans it created.
|
||||
|
||||
**Creates:** `{phase_num}-UAT.md`, fix plans if issues found
|
||||
|
||||
@@ -375,38 +375,38 @@ If everything passes, you move on. If something's broken, you don't manually deb
|
||||
### 6. Repeat → Ship → Complete → Next Milestone
|
||||
|
||||
```
|
||||
/gsd:discuss-phase 2
|
||||
/gsd:plan-phase 2
|
||||
/gsd:execute-phase 2
|
||||
/gsd:verify-work 2
|
||||
/gsd:ship 2 # Create PR from verified work
|
||||
/gsd-discuss-phase 2
|
||||
/gsd-plan-phase 2
|
||||
/gsd-execute-phase 2
|
||||
/gsd-verify-work 2
|
||||
/gsd-ship 2 # Create PR from verified work
|
||||
...
|
||||
/gsd:complete-milestone
|
||||
/gsd:new-milestone
|
||||
/gsd-complete-milestone
|
||||
/gsd-new-milestone
|
||||
```
|
||||
|
||||
Or let GSD figure out the next step automatically:
|
||||
|
||||
```
|
||||
/gsd:next # Auto-detect and run next step
|
||||
/gsd-next # Auto-detect and run next step
|
||||
```
|
||||
|
||||
Loop **discuss → plan → execute → verify → ship** until milestone complete.
|
||||
|
||||
If you want faster intake during discussion, use `/gsd:discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one. Use `--chain` to auto-chain discuss into plan+execute without stopping between steps.
|
||||
If you want faster intake during discussion, use `/gsd-discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one. Use `--chain` to auto-chain discuss into plan+execute without stopping between steps.
|
||||
|
||||
Each phase gets your input (discuss), proper research (plan), clean execution (execute), and human verification (verify). Context stays fresh. Quality stays high.
|
||||
|
||||
When all phases are done, `/gsd:complete-milestone` archives the milestone and tags the release.
|
||||
When all phases are done, `/gsd-complete-milestone` archives the milestone and tags the release.
|
||||
|
||||
Then `/gsd:new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.
|
||||
Then `/gsd-new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.
|
||||
|
||||
---
|
||||
|
||||
### Quick Mode
|
||||
|
||||
```
|
||||
/gsd:quick
|
||||
/gsd-quick
|
||||
```
|
||||
|
||||
**For ad-hoc tasks that don't need full planning.**
|
||||
@@ -428,7 +428,7 @@ Quick mode gives you GSD guarantees (atomic commits, state tracking) with a fast
|
||||
Flags are composable: `--discuss --research --validate` gives discussion + research + plan-checking + verification.
|
||||
|
||||
```
|
||||
/gsd:quick
|
||||
/gsd-quick
|
||||
> What do you want to do? "Add dark mode toggle to settings"
|
||||
```
|
||||
|
||||
@@ -527,119 +527,119 @@ You're never locked in. The system adapts.
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
|
||||
| `/gsd:discuss-phase [N] [--auto] [--analyze] [--chain]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis, `--chain` auto-chains into plan+execute) |
|
||||
| `/gsd:plan-phase [N] [--auto] [--reviews]` | Research + plan + verify for a phase (`--reviews` loads codebase review findings) |
|
||||
| `/gsd:execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
|
||||
| `/gsd:verify-work [N]` | Manual user acceptance testing ¹ |
|
||||
| `/gsd:ship [N] [--draft]` | Create PR from verified phase work with auto-generated body |
|
||||
| `/gsd:next` | Automatically advance to the next logical workflow step |
|
||||
| `/gsd:fast <text>` | Inline trivial tasks — skips planning entirely, executes immediately |
|
||||
| `/gsd:audit-milestone` | Verify milestone achieved its definition of done |
|
||||
| `/gsd:complete-milestone` | Archive milestone, tag release |
|
||||
| `/gsd:new-milestone [name]` | Start next version: questions → research → requirements → roadmap |
|
||||
| `/gsd:forensics [desc]` | Post-mortem investigation of failed workflow runs (diagnoses stuck loops, missing artifacts, git anomalies) |
|
||||
| `/gsd:milestone-summary [version]` | Generate comprehensive project summary for team onboarding and review |
|
||||
| `/gsd-new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
|
||||
| `/gsd-discuss-phase [N] [--auto] [--analyze] [--chain]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis, `--chain` auto-chains into plan+execute) |
|
||||
| `/gsd-plan-phase [N] [--auto] [--reviews]` | Research + plan + verify for a phase (`--reviews` loads codebase review findings) |
|
||||
| `/gsd-execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
|
||||
| `/gsd-verify-work [N]` | Manual user acceptance testing ¹ |
|
||||
| `/gsd-ship [N] [--draft]` | Create PR from verified phase work with auto-generated body |
|
||||
| `/gsd-next` | Automatically advance to the next logical workflow step |
|
||||
| `/gsd-fast <text>` | Inline trivial tasks — skips planning entirely, executes immediately |
|
||||
| `/gsd-audit-milestone` | Verify milestone achieved its definition of done |
|
||||
| `/gsd-complete-milestone` | Archive milestone, tag release |
|
||||
| `/gsd-new-milestone [name]` | Start next version: questions → research → requirements → roadmap |
|
||||
| `/gsd-forensics [desc]` | Post-mortem investigation of failed workflow runs (diagnoses stuck loops, missing artifacts, git anomalies) |
|
||||
| `/gsd-milestone-summary [version]` | Generate comprehensive project summary for team onboarding and review |
|
||||
|
||||
### Workstreams
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:workstreams list` | Show all workstreams and their status |
|
||||
| `/gsd:workstreams create <name>` | Create a namespaced workstream for parallel milestone work |
|
||||
| `/gsd:workstreams switch <name>` | Switch active workstream |
|
||||
| `/gsd:workstreams complete <name>` | Complete and merge a workstream |
|
||||
| `/gsd-workstreams list` | Show all workstreams and their status |
|
||||
| `/gsd-workstreams create <name>` | Create a namespaced workstream for parallel milestone work |
|
||||
| `/gsd-workstreams switch <name>` | Switch active workstream |
|
||||
| `/gsd-workstreams complete <name>` | Complete and merge a workstream |
|
||||
|
||||
### Multi-Project Workspaces
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:new-workspace` | Create isolated workspace with repo copies (worktrees or clones) |
|
||||
| `/gsd:list-workspaces` | Show all GSD workspaces and their status |
|
||||
| `/gsd:remove-workspace` | Remove workspace and clean up worktrees |
|
||||
| `/gsd-new-workspace` | Create isolated workspace with repo copies (worktrees or clones) |
|
||||
| `/gsd-list-workspaces` | Show all GSD workspaces and their status |
|
||||
| `/gsd-remove-workspace` | Remove workspace and clean up worktrees |
|
||||
|
||||
### UI Design
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:ui-phase [N]` | Generate UI design contract (UI-SPEC.md) for frontend phases |
|
||||
| `/gsd:ui-review [N]` | Retroactive 6-pillar visual audit of implemented frontend code |
|
||||
| `/gsd-ui-phase [N]` | Generate UI design contract (UI-SPEC.md) for frontend phases |
|
||||
| `/gsd-ui-review [N]` | Retroactive 6-pillar visual audit of implemented frontend code |
|
||||
|
||||
### Navigation
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:progress` | Where am I? What's next? |
|
||||
| `/gsd:next` | Auto-detect state and run the next step |
|
||||
| `/gsd:help` | Show all commands and usage guide |
|
||||
| `/gsd:update` | Update GSD with changelog preview |
|
||||
| `/gsd:join-discord` | Join the GSD Discord community |
|
||||
| `/gsd:manager` | Interactive command center for managing multiple phases |
|
||||
| `/gsd-progress` | Where am I? What's next? |
|
||||
| `/gsd-next` | Auto-detect state and run the next step |
|
||||
| `/gsd-help` | Show all commands and usage guide |
|
||||
| `/gsd-update` | Update GSD with changelog preview |
|
||||
| `/gsd-join-discord` | Join the GSD Discord community |
|
||||
| `/gsd-manager` | Interactive command center for managing multiple phases |
|
||||
|
||||
### Brownfield
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:map-codebase [area]` | Analyze existing codebase before new-project |
|
||||
| `/gsd-map-codebase [area]` | Analyze existing codebase before new-project |
|
||||
|
||||
### Phase Management
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:add-phase` | Append phase to roadmap |
|
||||
| `/gsd:insert-phase [N]` | Insert urgent work between phases |
|
||||
| `/gsd:remove-phase [N]` | Remove future phase, renumber |
|
||||
| `/gsd:list-phase-assumptions [N]` | See Claude's intended approach before planning |
|
||||
| `/gsd:plan-milestone-gaps` | Create phases to close gaps from audit |
|
||||
| `/gsd-add-phase` | Append phase to roadmap |
|
||||
| `/gsd-insert-phase [N]` | Insert urgent work between phases |
|
||||
| `/gsd-remove-phase [N]` | Remove future phase, renumber |
|
||||
| `/gsd-list-phase-assumptions [N]` | See Claude's intended approach before planning |
|
||||
| `/gsd-plan-milestone-gaps` | Create phases to close gaps from audit |
|
||||
|
||||
### Session
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:pause-work` | Create handoff when stopping mid-phase (writes HANDOFF.json) |
|
||||
| `/gsd:resume-work` | Restore from last session |
|
||||
| `/gsd:session-report` | Generate session summary with work performed and outcomes |
|
||||
| `/gsd-pause-work` | Create handoff when stopping mid-phase (writes HANDOFF.json) |
|
||||
| `/gsd-resume-work` | Restore from last session |
|
||||
| `/gsd-session-report` | Generate session summary with work performed and outcomes |
|
||||
|
||||
### Workstreams
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:workstreams` | Manage parallel workstreams (list, create, switch, status, progress, complete) |
|
||||
| `/gsd-workstreams` | Manage parallel workstreams (list, create, switch, status, progress, complete) |
|
||||
|
||||
### Code Quality
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:review` | Cross-AI peer review of current phase or branch |
|
||||
| `/gsd:secure-phase [N]` | Security enforcement with threat-model-anchored verification |
|
||||
| `/gsd:pr-branch` | Create clean PR branch filtering `.planning/` commits |
|
||||
| `/gsd:audit-uat` | Audit verification debt — find phases missing UAT |
|
||||
| `/gsd:docs-update` | Verified documentation generation with doc-writer and doc-verifier agents |
|
||||
| `/gsd-review` | Cross-AI peer review of current phase or branch |
|
||||
| `/gsd-secure-phase [N]` | Security enforcement with threat-model-anchored verification |
|
||||
| `/gsd-pr-branch` | Create clean PR branch filtering `.planning/` commits |
|
||||
| `/gsd-audit-uat` | Audit verification debt — find phases missing UAT |
|
||||
| `/gsd-docs-update` | Verified documentation generation with doc-writer and doc-verifier agents |
|
||||
|
||||
### Backlog & Threads
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:plant-seed <idea>` | Capture forward-looking ideas with trigger conditions — surfaces at the right milestone |
|
||||
| `/gsd:add-backlog <desc>` | Add idea to backlog parking lot (999.x numbering, outside active sequence) |
|
||||
| `/gsd:review-backlog` | Review and promote backlog items to active milestone or remove stale entries |
|
||||
| `/gsd:thread [name]` | Persistent context threads — lightweight cross-session knowledge for work spanning multiple sessions |
|
||||
| `/gsd-plant-seed <idea>` | Capture forward-looking ideas with trigger conditions — surfaces at the right milestone |
|
||||
| `/gsd-add-backlog <desc>` | Add idea to backlog parking lot (999.x numbering, outside active sequence) |
|
||||
| `/gsd-review-backlog` | Review and promote backlog items to active milestone or remove stale entries |
|
||||
| `/gsd-thread [name]` | Persistent context threads — lightweight cross-session knowledge for work spanning multiple sessions |
|
||||
|
||||
### Utilities
|
||||
|
||||
| Command | What it does |
|
||||
|---------|--------------|
|
||||
| `/gsd:settings` | Configure model profile and workflow agents |
|
||||
| `/gsd:set-profile <profile>` | Switch model profile (quality/balanced/budget/inherit) |
|
||||
| `/gsd:add-todo [desc]` | Capture idea for later |
|
||||
| `/gsd:check-todos` | List pending todos |
|
||||
| `/gsd:debug [desc]` | Systematic debugging with persistent state |
|
||||
| `/gsd:do <text>` | Route freeform text to the right GSD command automatically |
|
||||
| `/gsd:note <text>` | Zero-friction idea capture — append, list, or promote notes to todos |
|
||||
| `/gsd:quick [--full] [--validate] [--discuss] [--research]` | Execute ad-hoc task with GSD guarantees (`--full` enables all phases, `--validate` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
|
||||
| `/gsd:health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
|
||||
| `/gsd:stats` | Display project statistics — phases, plans, requirements, git metrics |
|
||||
| `/gsd:profile-user [--questionnaire] [--refresh]` | Generate developer behavioral profile from session analysis for personalized responses |
|
||||
| `/gsd-settings` | Configure model profile and workflow agents |
|
||||
| `/gsd-set-profile <profile>` | Switch model profile (quality/balanced/budget/inherit) |
|
||||
| `/gsd-add-todo [desc]` | Capture idea for later |
|
||||
| `/gsd-check-todos` | List pending todos |
|
||||
| `/gsd-debug [desc]` | Systematic debugging with persistent state |
|
||||
| `/gsd-do <text>` | Route freeform text to the right GSD command automatically |
|
||||
| `/gsd-note <text>` | Zero-friction idea capture — append, list, or promote notes to todos |
|
||||
| `/gsd-quick [--full] [--validate] [--discuss] [--research]` | Execute ad-hoc task with GSD guarantees (`--full` enables all phases, `--validate` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
|
||||
| `/gsd-health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
|
||||
| `/gsd-stats` | Display project statistics — phases, plans, requirements, git metrics |
|
||||
| `/gsd-profile-user [--questionnaire] [--refresh]` | Generate developer behavioral profile from session analysis for personalized responses |
|
||||
|
||||
<sup>¹ Contributed by reddit user OracleGreyBeard</sup>
|
||||
|
||||
@@ -647,7 +647,7 @@ You're never locked in. The system adapts.
|
||||
|
||||
## Configuration
|
||||
|
||||
GSD stores project settings in `.planning/config.json`. Configure during `/gsd:new-project` or update later with `/gsd:settings`. For the full config schema, workflow toggles, git branching options, and per-agent model breakdown, see the [User Guide](docs/USER-GUIDE.md#configuration-reference).
|
||||
GSD stores project settings in `.planning/config.json`. Configure during `/gsd-new-project` or update later with `/gsd-settings`. For the full config schema, workflow toggles, git branching options, and per-agent model breakdown, see the [User Guide](docs/USER-GUIDE.md#configuration-reference).
|
||||
|
||||
### Core Settings
|
||||
|
||||
@@ -670,12 +670,12 @@ Control which Claude model each agent uses. Balance quality vs token spend.
|
||||
|
||||
Switch profiles:
|
||||
```
|
||||
/gsd:set-profile budget
|
||||
/gsd-set-profile budget
|
||||
```
|
||||
|
||||
Use `inherit` when using non-Anthropic providers (OpenRouter, local models) or to follow the current runtime model selection (e.g. OpenCode `/model`).
|
||||
|
||||
Or configure via `/gsd:settings`.
|
||||
Or configure via `/gsd-settings`.
|
||||
|
||||
### Workflow Agents
|
||||
|
||||
@@ -693,9 +693,9 @@ These spawn additional agents during planning/execution. They improve quality bu
|
||||
| `workflow.text_mode` | `false` | Text-only mode for remote sessions (no TUI menus) |
|
||||
| `workflow.use_worktrees` | `true` | Toggle worktree isolation for execution |
|
||||
|
||||
Use `/gsd:settings` to toggle these, or override per-invocation:
|
||||
- `/gsd:plan-phase --skip-research`
|
||||
- `/gsd:plan-phase --skip-verify`
|
||||
Use `/gsd-settings` to toggle these, or override per-invocation:
|
||||
- `/gsd-plan-phase --skip-research`
|
||||
- `/gsd-plan-phase --skip-verify`
|
||||
|
||||
### Execution
|
||||
|
||||
@@ -787,7 +787,7 @@ This prevents Claude from reading these files entirely, regardless of what comma
|
||||
- For Codex, verify skills exist in `~/.codex/skills/gsd-*/SKILL.md` (global) or `./.codex/skills/gsd-*/SKILL.md` (local)
|
||||
|
||||
**Commands not working as expected?**
|
||||
- Run `/gsd:help` to verify installation
|
||||
- Run `/gsd-help` to verify installation
|
||||
- Re-run `npx get-shit-done-cc` to reinstall
|
||||
|
||||
**Updating to the latest version?**
|
||||
|
||||
Reference in New Issue
Block a user