@undeemed/get-shit-done-codex 1.20.10 → 1.22.0

package/.codex/config.toml

@@ -0,0 +1,77 @@
+:schema https://developers.openai.com/codex/config-schema.json
+
+# Project-scoped Codex config for get-shit-done-codex.
+# Loaded only when this project is trusted.
+# Docs:
+# - https://developers.openai.com/codex/config-basic
+# - https://developers.openai.com/codex/config-reference
+# - https://developers.openai.com/codex/multi-agent
+
+web_search = "live"
+
+[features]
+multi_agent = true
+collaboration_modes = true
+shell_tool = true
+shell_snapshot = true
+unified_exec = true
+apply_patch_freeform = true
+personality = true
+request_rule = true
+
+[agents]
+max_threads = 12
+max_depth = 3
+
+[agents."general-purpose"]
+description = "General fallback role for GSD orchestration and ad-hoc subtasks."
+
+[agents."gsd-codebase-mapper"]
+description = "Map stack, architecture, conventions, testing, and concerns into .planning/codebase docs."
+developer_instructions = "Read and follow agents/gsd-codebase-mapper.md for your complete role definition."
+
+[agents."gsd-debugger"]
+description = "Investigate regressions with hypothesis testing, isolate root cause, and propose or apply fixes."
+developer_instructions = "Read and follow agents/gsd-debugger.md for your complete role definition."
+
+[agents."gsd-executor"]
+description = "Execute PLAN.md tasks with atomic commits, verification, and summary updates."
+developer_instructions = "Read and follow agents/gsd-executor.md for your complete role definition."
+
+[agents."gsd-integration-checker"]
+description = "Verify cross-phase wiring and end-to-end behavior across delivered milestones."
+developer_instructions = "Read and follow agents/gsd-integration-checker.md for your complete role definition."
+
+[agents."gsd-phase-researcher"]
+description = "Research phase implementation patterns and write RESEARCH.md artifacts for planners."
+developer_instructions = "Read and follow agents/gsd-phase-researcher.md for your complete role definition."
+
+[agents."gsd-plan-checker"]
+description = "Stress-test plan quality and requirement coverage before execution."
+developer_instructions = "Read and follow agents/gsd-plan-checker.md for your complete role definition."
+
+[agents."gsd-planner"]
+description = "Draft atomic PLAN.md files with objective, context, tasks, and success criteria."
+developer_instructions = "Read and follow agents/gsd-planner.md for your complete role definition."
+
+[agents."gsd-project-researcher"]
+description = "Research ecosystem and produce project-level research docs for roadmap creation."
+developer_instructions = "Read and follow agents/gsd-project-researcher.md for your complete role definition."
+
+[agents."gsd-research-synthesizer"]
+description = "Synthesize parallel research artifacts into actionable roadmap inputs."
+developer_instructions = "Read and follow agents/gsd-research-synthesizer.md for your complete role definition."
+
+[agents."gsd-roadmapper"]
+description = "Turn requirements into phased ROADMAP.md structure with clear success criteria."
+developer_instructions = "Read and follow agents/gsd-roadmapper.md for your complete role definition."
+
+[agents."gsd-verifier"]
+description = "Perform goal-backward verification that outcomes are actually delivered in code."
+developer_instructions = "Read and follow agents/gsd-verifier.md for your complete role definition."
+
+[mcp_servers.context7]
+url = "https://mcp.context7.com/mcp"
+
+[mcp_servers.context7.env_http_headers]
+CONTEXT7_API_KEY = "CONTEXT7_API_KEY"

package/README.md

@@ -21,10 +21,13 @@ get-shit-done-codex (GSD) solves context rot — the quality degradation that ha
 
 ## What Changed In This Fork
 
-- **AGENTS-first for Codex:** `AGENTS.md` is the primary behavior contract  . [Agent.md > Skills.md](https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals)
-- **Two command surfaces:** choose native skills (`$gsd-*`) or prompt aliases (`/prompts:gsd-*`).
-- **Installer integrity checks:** `--verify` audits installation health, `--repair` restores missing artifacts.
-- **Mode-aware installs:** installer adapts `AGENTS.md` and command guidance to your chosen mode.
+- **AGENTS-first for Codex:** `AGENTS.md` is the primary behavior contract. [Agent.md > Skills.md](https://vercel.com/blog/agents-md-outperforms-skills-in-our-agent-evals)
+- **Native skills:** all commands use `$gsd-*` skill notation — no prompt aliases needed.
+- **Full config distribution:** installer ships `.codex/config.toml` (multi-agent, feature flags, MCP servers) and 11 rich `agents/*.md` sub-agent definitions — everything needed for multi-agent orchestration out of the box.
+- **Sub-agent linking:** each agent role in `config.toml` uses `developer_instructions` to load its full role definition from `agents/gsd-*.md` at runtime — no manual wiring needed.
+- **Overwrite protection:** `config.toml` is never overwritten on reinstall. `AGENTS.md` prompts for confirmation on global installs.
+- **Installer integrity checks:** `--verify` audits `AGENTS.md`, `config.toml`, agent definitions, command surfaces, and version metadata. `--repair` restores missing artifacts.
+- **One-click trust:** Codex prompts to trust the project on first run so the config takes effect.
 
 ## Installation
 
@@ -40,51 +43,39 @@ You can install globally (`~/.codex/`) or locally (`./`).
 npx @undeemed/get-shit-done-codex --global
 ```
 
-If you run this in an interactive terminal, the installer will prompt you to choose `skills` (`$`) or `prompts` (`/prompts`).
-In non-interactive runs, default is `skills` mode.
-
-For non-interactive installs:
-
 ```bash
 npx @undeemed/get-shit-done-codex --global   # Install to ~/.codex/
 npx @undeemed/get-shit-done-codex --local    # Install to current directory
-npx @undeemed/get-shit-done-codex --global --codex-mode skills   # Native skills only
-npx @undeemed/get-shit-done-codex --global --codex-mode prompts  # Prompt aliases only
-npx @undeemed/get-shit-done-codex --global --migrate             # Apply detected migration cleanup
-npx @undeemed/get-shit-done-codex --global --skip-migrate        # Keep legacy surface files
+npx @undeemed/get-shit-done-codex --global --migrate             # Clean up legacy prompts/
 npx @undeemed/get-shit-done-codex --verify --global              # Check install integrity
 npx @undeemed/get-shit-done-codex --verify --repair --global     # Auto-repair
 ```
 
-### Codex Modes
+After installation, run `codex` (CLI) or `codex app` (Desktop), then run `$gsd-help`.
 
-| Mode      | Installs                     | Use Commands Like           |
-| --------- | ---------------------------- | --------------------------- |
-| `skills` (default) | `skills/gsd-*/SKILL.md`      | `$gsd-help`, `$gsd-plan-phase 1` |
-| `prompts` | `prompts/gsd-*.md`           | `/prompts:gsd-help`         |
+### What Gets Installed
 
-After installation, run `codex` (CLI) or `codex app` (Desktop), then run `$gsd-help` (or `/prompts:gsd-help` in prompts mode).
-Single-surface policy: mixed `skills/` + `prompts/` installs are treated as drift and fail `--verify`.
+The installer distributes everything GSD needs:
 
-### Installed File Structure
+- **`AGENTS.md`** — behavior contract and command reference for Codex
+- **`.codex/config.toml`** — multi-agent mode, feature flags, agent role registry, MCP servers
+- **`agents/gsd-*.md`** — rich agent definitions (700+ lines each) for sub-agent orchestration
+- **`skills/gsd-*/SKILL.md`** — native Codex skill commands
+- **`get-shit-done/`** — workflow files, templates, and references
 
-`$` skills mode (`--codex-mode skills`, default):
+On first run, Codex will prompt you to **trust the project** so the config takes effect (one-time, one-click).
 
-```text
-~/.codex/
-├── AGENTS.md
-├── skills/
-│   └── gsd-*/SKILL.md
-└── get-shit-done/
-```
+> [!NOTE]
+> `.codex/config.toml` is non-destructive — the installer skips it if you already have one, so your customizations are preserved on updates.
 
-`/prompts` mode (`--codex-mode prompts`):
+### Installed File Structure
 
 ```text
 ~/.codex/
 ├── AGENTS.md
-├── prompts/
-│   └── gsd-*.md
+├── .codex/config.toml
+├── agents/gsd-*.md
+├── skills/gsd-*/SKILL.md
 └── get-shit-done/
 ```
 
@@ -92,7 +83,7 @@ For local installs, replace `~/.codex/` with `./`.
 
 ### Verify And Repair
 
-- `--verify`: checks `AGENTS.md`, command surfaces, workflow assets, and version metadata.
+- `--verify`: checks `AGENTS.md`, `config.toml`, agent definitions, command surfaces, workflow assets, and version metadata.
 - `--verify --repair`: reinstalls missing/broken artifacts and verifies again.
 - Migration is **detect-then-confirm**, not automatic:
   - Interactive install asks before removing legacy surface files
@@ -105,20 +96,18 @@ This fork is intentionally **AGENTS.md-first** for Codex reliability:
 
 - `AGENTS.md` is the source of truth for behavior and workflow constraints
 - `$gsd-*` skills are lightweight command wrappers around the same workflow docs
-- `/prompts:gsd-*` are optional compatibility aliases (prompts mode)
 
 ## Staying Updated
 
 ```bash
 # Check for updates from inside Codex
 $gsd-update
-# or: /prompts:gsd-update
 
 # Update from terminal
 npx @undeemed/get-shit-done-codex@latest --global
 ```
 
-The installer writes a `get-shit-done/VERSION` file so `$gsd-update` (or `/prompts:gsd-update`) can detect installed vs latest and show changelog before updating.
+The installer writes a `get-shit-done/VERSION` file so `$gsd-update` can detect installed vs latest and show changelog before updating.
 
 ## npm Trusted Publisher (OIDC)
 
@@ -205,8 +194,6 @@ Manual user acceptance testing. The system walks you through testable deliverabl
 | `$gsd-verify-work [N]`   | Manual user acceptance testing                                    |
 | `$gsd-help`              | Show all commands                                                 |
 
-Use `/prompts:gsd-*` aliases when installed with `--codex-mode prompts`.
-
 ## Why It Works
 
 ### Context Engineering
@@ -231,6 +218,26 @@ Every stage uses a thin orchestrator that spawns specialized agents:
 
 The orchestrator stays at 30-40% context. The work happens in fresh subagent contexts.
 
+### Sub-Agent Roles
+
+GSD ships 11 specialized agent definitions in `agents/gsd-*.md`, each wired into `config.toml` via `developer_instructions`:
+
+| Agent                      | Role                                                       |
+| -------------------------- | ---------------------------------------------------------- |
+| `gsd-planner`              | Draft atomic PLAN.md files with tasks and success criteria |
+| `gsd-executor`             | Execute plans with atomic commits and verification         |
+| `gsd-verifier`             | Goal-backward verification that outcomes are delivered     |
+| `gsd-debugger`             | Hypothesis testing, root cause isolation, fix proposals    |
+| `gsd-phase-researcher`     | Research implementation patterns for planners              |
+| `gsd-project-researcher`   | Ecosystem research for roadmap creation                    |
+| `gsd-research-synthesizer` | Synthesize parallel research into actionable inputs        |
+| `gsd-plan-checker`         | Stress-test plan quality and requirement coverage          |
+| `gsd-codebase-mapper`      | Map stack, architecture, and conventions                   |
+| `gsd-roadmapper`           | Turn requirements into phased roadmaps                     |
+| `gsd-integration-checker`  | Verify cross-phase wiring and e2e behavior                 |
+
+Each agent gets its full role definition (700+ lines) loaded at spawn time — no context wasted on the orchestrator.
+
 ### Atomic Git Commits
 
 Each task gets its own commit immediately after completion:
@@ -249,7 +256,12 @@ Git bisect finds exact failing task. Each task independently revertable.
 
 - Restart Codex to reload installed command surfaces
 - Check `~/.codex/skills/gsd-*/SKILL.md` (global) or `./skills/gsd-*/SKILL.md` (local)
-- If using prompt aliases, check `~/.codex/prompts/gsd-*.md` (global) or `./prompts/gsd-*.md` (local)
+
+**Multi-agent / sub-agents not working?**
+
+- Check `.codex/config.toml` exists in your install directory
+- Ensure the project is **trusted** in Codex (it prompts on first run)
+- Run `--verify` to check all artifacts are present
 
 **Update to latest:**
 
@@ -260,7 +272,7 @@ npx @undeemed/get-shit-done-codex@latest
 **Can users be notified when an update is available?**
 
 - Yes. The installer prints an update notice if a newer npm version exists.
-- In-Codex update checks are available via `$gsd-update` (or `/prompts:gsd-update`).
+- In-Codex update checks are available via `$gsd-update`.
 - For release notifications outside the CLI, enable GitHub release watching on this repo.
 
 ## More Documentation
@@ -277,8 +289,7 @@ The original repository contains:
 
 **Note:** The original README is written for Codex Code. When following it, remember that this fork uses:
 
-- Codex-native skills (`$gsd-*`) by default
-- Optional prompt aliases (`/prompts:gsd-*`) via `--codex-mode prompts`
+- Codex-native skills (`$gsd-*`)
 - OpenAI Codex CLI & Desktop
 
 ## Keywords

package/agents/gsd-codebase-mapper.md

@@ -8,7 +8,7 @@ color: cyan
 <role>
 You are a GSD codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to `.planning/codebase/`.
 
-You are spawned by `/gsd:map-codebase` with one of four focus areas:
+You are spawned by `$gsd-map-codebase` with one of four focus areas:
 - **tech**: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
 - **arch**: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
 - **quality**: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
@@ -23,7 +23,7 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 <why_this_matters>
 **These documents are consumed by other GSD commands:**
 
-**`/gsd:plan-phase`** loads relevant codebase docs when creating implementation plans:
+**`$gsd-plan-phase`** loads relevant codebase docs when creating implementation plans:
 | Phase Type | Documents Loaded |
 |------------|------------------|
 | UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
@@ -34,7 +34,7 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 | refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
 | setup, config | STACK.md, STRUCTURE.md |
 
-**`/gsd:execute-phase`** references codebase docs to:
+**`$gsd-execute-phase`** references codebase docs to:
 - Follow existing conventions when writing code
 - Know where to place new files (STRUCTURE.md)
 - Match testing patterns (TESTING.md)

package/agents/gsd-debugger.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-debugger
-description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
+description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by $gsd-debug orchestrator.
 tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch
 color: orange
 ---
@@ -10,7 +10,7 @@ You are a GSD debugger. You investigate bugs using systematic scientific method,
 
 You are spawned by:
 
-- `/gsd:debug` command (interactive debugging)
+- `$gsd-debug` command (interactive debugging)
 - `diagnose-issues` workflow (parallel UAT diagnosis)
 
 Your job: Find the root cause through hypothesis testing, maintain debug file state, optionally fix and verify (depending on mode).
@@ -897,7 +897,7 @@ Gather symptoms through questioning. Update file after EACH answer.
   - Otherwise -> proceed to fix_and_verify
 - **ELIMINATED:** Append to Eliminated section, form new hypothesis, return to Phase 2
 
-**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run /gsd:debug to resume" if context filling up.
+**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run $gsd-debug to resume" if context filling up.
 </step>
 
 <step name="resume_from_file">
@@ -1027,7 +1027,7 @@ mv .planning/debug/{slug}.md .planning/debug/resolved/
 **Check planning config using state load (commit_docs is available from the output):**
 
 ```bash
-INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs state load)
+INIT=$(node ./get-shit-done/bin/gsd-tools.cjs state load)
 # commit_docs is in the JSON output
 ```
 
@@ -1044,7 +1044,7 @@ Root cause: {root_cause}"
 
 Then commit planning docs via CLI (respects `commit_docs` config automatically):
 ```bash
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs: resolve debug {slug}" --files .planning/debug/resolved/{slug}.md
+node ./get-shit-done/bin/gsd-tools.cjs commit "docs: resolve debug {slug}" --files .planning/debug/resolved/{slug}.md
 ```
 
 Report completion and offer next steps.

package/agents/gsd-executor.md

@@ -8,7 +8,7 @@ color: yellow
 <role>
 You are a GSD plan executor. You execute PLAN.md files atomically, creating per-task commits, handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
 
-Spawned by `/gsd:execute-phase` orchestrator.
+Spawned by `$gsd-execute-phase` orchestrator.
 
 Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
 
@@ -37,7 +37,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
 Load execution context:
 
 ```bash
-INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init execute-phase "${PHASE}")
+INIT=$(node ./get-shit-done/bin/gsd-tools.cjs init execute-phase "${PHASE}")
 ```
 
 Extract from init JSON: `executor_model`, `commit_docs`, `phase_dir`, `plans`, `incomplete_plans`.
@@ -190,7 +190,7 @@ Track auto-fix attempts per task. After 3 auto-fix attempts on a single task:
 Check if auto mode is active at executor start:
 
 ```bash
-AUTO_CFG=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs config-get workflow.auto_advance 2>/dev/null || echo "false")
+AUTO_CFG=$(node ./get-shit-done/bin/gsd-tools.cjs config-get workflow.auto_advance 2>/dev/null || echo "false")
 ```
 
 Store the result for checkpoint handling below.
@@ -203,7 +203,7 @@ Store the result for checkpoint handling below.
 Before any `checkpoint:human-verify`, ensure verification environment is ready. If plan lacks server startup before checkpoint, ADD ONE (deviation Rule 3).
 
 For full automation-first patterns, server lifecycle, CLI handling:
-**See @~/.codex/get-shit-done/references/checkpoints.md**
+**See @./get-shit-done/references/checkpoints.md**
 
 **Quick reference:** Users NEVER run CLI commands. Users ONLY visit URLs, click UI, evaluate visuals, provide secrets. Codex does all automation.
 
@@ -326,7 +326,7 @@ After all tasks complete, create `{phase}-{plan}-SUMMARY.md` at `.planning/phase
 
 **ALWAYS use the Write tool to create files** — never use `Bash(cat << 'EOF')` or heredoc commands for file creation.
 
-**Use template:** @~/.codex/get-shit-done/templates/summary.md
+**Use template:** @./get-shit-done/templates/summary.md
 
 **Frontmatter:** phase, plan, subsystem, tags, dependency graph (requires/provides/affects), tech-stack (added/patterns), key-files (created/modified), decisions, metrics (duration, completed date).
 
@@ -379,34 +379,34 @@ After SUMMARY.md, update STATE.md using gsd-tools:
 
 ```bash
 # Advance plan counter (handles edge cases automatically)
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs state advance-plan
+node ./get-shit-done/bin/gsd-tools.cjs state advance-plan
 
 # Recalculate progress bar from disk state
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs state update-progress
+node ./get-shit-done/bin/gsd-tools.cjs state update-progress
 
 # Record execution metrics
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs state record-metric \
+node ./get-shit-done/bin/gsd-tools.cjs state record-metric \
   --phase "${PHASE}" --plan "${PLAN}" --duration "${DURATION}" \
   --tasks "${TASK_COUNT}" --files "${FILE_COUNT}"
 
 # Add decisions (extract from SUMMARY.md key-decisions)
 for decision in "${DECISIONS[@]}"; do
-  node ~/.codex/get-shit-done/bin/gsd-tools.cjs state add-decision \
+  node ./get-shit-done/bin/gsd-tools.cjs state add-decision \
     --phase "${PHASE}" --summary "${decision}"
 done
 
 # Update session info
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs state record-session \
+node ./get-shit-done/bin/gsd-tools.cjs state record-session \
   --stopped-at "Completed ${PHASE}-${PLAN}-PLAN.md"
 ```
 
 ```bash
 # Update ROADMAP.md progress for this phase (plan counts, status)
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs roadmap update-plan-progress "${PHASE_NUMBER}"
+node ./get-shit-done/bin/gsd-tools.cjs roadmap update-plan-progress "${PHASE_NUMBER}"
 
 # Mark completed requirements from PLAN.md frontmatter
 # Extract the `requirements` array from the plan's frontmatter, then mark each complete
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs requirements mark-complete ${REQ_IDS}
+node ./get-shit-done/bin/gsd-tools.cjs requirements mark-complete ${REQ_IDS}
 ```
 
 **Requirement IDs:** Extract from the PLAN.md frontmatter `requirements:` field (e.g., `requirements: [AUTH-01, AUTH-02]`). Pass all IDs to `requirements mark-complete`. If the plan has no requirements field, skip this step.
@@ -424,13 +424,13 @@ node ~/.codex/get-shit-done/bin/gsd-tools.cjs requirements mark-complete ${REQ_I
 
 **For blockers found during execution:**
 ```bash
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs state add-blocker "Blocker description"
+node ./get-shit-done/bin/gsd-tools.cjs state add-blocker "Blocker description"
 ```
 </state_updates>
 
 <final_commit>
 ```bash
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs({phase}-{plan}): complete [plan-name] plan" --files .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .planning/STATE.md .planning/ROADMAP.md .planning/REQUIREMENTS.md
+node ./get-shit-done/bin/gsd-tools.cjs commit "docs({phase}-{plan}): complete [plan-name] plan" --files .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .planning/STATE.md .planning/ROADMAP.md .planning/REQUIREMENTS.md
 ```
 
 Separate from per-task commits — captures execution results only.

package/agents/gsd-phase-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-phase-researcher
-description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
+description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by $gsd-plan-phase orchestrator.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*
 color: cyan
 ---
@@ -8,7 +8,7 @@ color: cyan
 <role>
 You are a GSD phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
 
-Spawned by `/gsd:plan-phase` (integrated) or `/gsd:research-phase` (standalone).
+Spawned by `$gsd-plan-phase` (integrated) or `$gsd-research-phase` (standalone).
 
 **CRITICAL: Mandatory Initial Read**
 If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
@@ -37,7 +37,7 @@ This ensures research aligns with project-specific conventions and libraries.
 </project_context>
 
 <upstream_input>
-**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
+**CONTEXT.md** (if exists) — User decisions from `$gsd-discuss-phase`
 
 | Section | How You Use It |
 |---------|----------------|
@@ -120,7 +120,7 @@ When researching "best library for X": find what the ecosystem actually uses, do
 Check `brave_search` from init context. If `true`, use Brave Search for higher quality results:
 
 ```bash
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs websearch "your query" --limit 10
+node ./get-shit-done/bin/gsd-tools.cjs websearch "your query" --limit 10
 ```
 
 **Options:**
@@ -317,7 +317,7 @@ Verified patterns from official sources:
 ### Nyquist Sampling Rate
 - **Minimum sample interval:** After every committed task → run: `{quick run command}`
 - **Full suite trigger:** Before merging final task of any plan wave
-- **Phase-complete gate:** Full suite green before `/gsd:verify-work` runs
+- **Phase-complete gate:** Full suite green before `$gsd-verify-work` runs
 - **Estimated feedback latency per task:** ~{N} seconds
 
 ### Wave 0 Gaps (must be created before implementation)
@@ -361,7 +361,7 @@ Orchestrator provides: phase number/name, description/goal, requirements, constr
 
 Load phase context using init command:
 ```bash
-INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE}")
+INIT=$(node ./get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE}")
 ```
 
 Extract from init JSON: `phase_dir`, `padded_phase`, `phase_number`, `commit_docs`.
@@ -476,7 +476,7 @@ Write to: `$PHASE_DIR/$PADDED_PHASE-RESEARCH.md`
 ## Step 7: Commit Research (optional)
 
 ```bash
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs($PHASE): research phase domain" --files "$PHASE_DIR/$PADDED_PHASE-RESEARCH.md"
+node ./get-shit-done/bin/gsd-tools.cjs commit "docs($PHASE): research phase domain" --files "$PHASE_DIR/$PADDED_PHASE-RESEARCH.md"
 ```
 
 ## Step 8: Return Structured Result

package/agents/gsd-plan-checker.md

@@ -1,6 +1,6 @@
 ---
 name: gsd-plan-checker
-description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
+description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by $gsd-plan-phase orchestrator.
 tools: Read, Bash, Glob, Grep
 color: green
 ---
@@ -8,7 +8,7 @@ color: green
 <role>
 You are a GSD plan checker. Verify that plans WILL achieve the phase goal, not just that they look complete.
 
-Spawned by `/gsd:plan-phase` orchestrator (after planner creates PLAN.md) or re-verification (after planner revises).
+Spawned by `$gsd-plan-phase` orchestrator (after planner creates PLAN.md) or re-verification (after planner revises).
 
 Goal-backward verification of PLANS before execution. Start from what the phase SHOULD deliver, verify plans address it.
 
@@ -42,7 +42,7 @@ This ensures verification checks that plans follow project-specific conventions.
 </project_context>
 
 <upstream_input>
-**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
+**CONTEXT.md** (if exists) — User decisions from `$gsd-discuss-phase`
 
 | Section | How You Use It |
 |---------|----------------|
@@ -271,7 +271,7 @@ issue:
 
 ## Dimension 7: Context Compliance (if CONTEXT.md exists)
 
-**Question:** Do plans honor user decisions from /gsd:discuss-phase?
+**Question:** Do plans honor user decisions from $gsd-discuss-phase?
 
 **Only check if CONTEXT.md was provided in the verification context.**
 
@@ -419,7 +419,7 @@ If Dimension 8 FAILS:
 
 Load phase operation context:
 ```bash
-INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE_ARG}")
+INIT=$(node ./get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE_ARG}")
 ```
 
 Extract from init JSON: `phase_dir`, `phase_number`, `has_plans`, `plan_count`.
@@ -430,7 +430,7 @@ Orchestrator provides CONTEXT.md content in the verification prompt. If provided
 ls "$phase_dir"/*-PLAN.md 2>/dev/null
 # Read research for Nyquist validation data
 cat "$phase_dir"/*-RESEARCH.md 2>/dev/null
-node ~/.codex/get-shit-done/bin/gsd-tools.cjs roadmap get-phase "$phase_number"
+node ./get-shit-done/bin/gsd-tools.cjs roadmap get-phase "$phase_number"
 ls "$phase_dir"/*-BRIEF.md 2>/dev/null
 ```
 
@@ -443,7 +443,7 @@ Use gsd-tools to validate plan structure:
 ```bash
 for plan in "$PHASE_DIR"/*-PLAN.md; do
   echo "=== $plan ==="
-  PLAN_STRUCTURE=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs verify plan-structure "$plan")
+  PLAN_STRUCTURE=$(node ./get-shit-done/bin/gsd-tools.cjs verify plan-structure "$plan")
   echo "$PLAN_STRUCTURE"
 done
 ```
@@ -461,7 +461,7 @@ Map errors/warnings to verification dimensions:
 Extract must_haves from each plan using gsd-tools:
 
 ```bash
-MUST_HAVES=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs frontmatter get "$PLAN_PATH" --field must_haves)
+MUST_HAVES=$(node ./get-shit-done/bin/gsd-tools.cjs frontmatter get "$PLAN_PATH" --field must_haves)
 ```
 
 Returns JSON: `{ truths: [...], artifacts: [...], key_links: [...] }`
@@ -504,7 +504,7 @@ For each requirement: find covering task(s), verify action is specific, flag gap
 Use gsd-tools plan-structure verification (already run in Step 2):
 
 ```bash
-PLAN_STRUCTURE=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs verify plan-structure "$PLAN_PATH")
+PLAN_STRUCTURE=$(node ./get-shit-done/bin/gsd-tools.cjs verify plan-structure "$PLAN_PATH")
 ```
 
 The `tasks` array in the result shows each task's completeness:
@@ -666,7 +666,7 @@ Return all issues as a structured `issues:` YAML list (see dimension examples fo
 | 01   | 3     | 5     | 1    | Valid  |
 | 02   | 2     | 4     | 2    | Valid  |
 
-Plans verified. Run `/gsd:execute-phase {phase}` to proceed.
+Plans verified. Run `$gsd-execute-phase {phase}` to proceed.
 ```
 
 ## ISSUES FOUND