gsd-codex-cli 1.20.9 → 1.20.11

package/.codex/prompts/gsd-add-phase.md

@@ -30,12 +30,6 @@ Add phase to end of current milestone in roadmap
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse <description> from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-add-todo.md

@@ -30,12 +30,6 @@ Capture idea or task as todo from current conversation context
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse [optional description] from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-audit-milestone.md

@@ -30,12 +30,6 @@ Audit milestone completion against original intent before archiving
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[version]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-check-todos.md

@@ -30,12 +30,6 @@ List pending todos and select one to work on
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse [area filter] from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-complete-milestone.md

@@ -30,12 +30,6 @@ Archive completed milestone and prepare for next version
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse <version> from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-debug.md

@@ -30,12 +30,6 @@ Systematic debugging with persistent state across context resets
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse [issue description] from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -55,5 +49,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-discuss-phase.md

@@ -30,12 +30,6 @@ Gather phase context through adaptive questioning before planning
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "<phase>" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: `gsd-plan-phase [phase]` (Codex) / `/gsd:plan-phase [phase]` (Claude)
+- Next recommended command: `/prompts:gsd-plan-phase [phase]` (Codex) / `/gsd:plan-phase [phase]` (Claude)
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-doctor.md

@@ -1,7 +1,11 @@
 ---
 description: Diagnose Codex+Claude GSD installation (engine, prompts, versions)
 argument-hint: [none]
----## Objective
+---
+
+$ARGUMENTS
+
+## Objective
 Diagnose whether this project is set up to run GSD prompts in Codex while remaining compatible with Claude workflows on the same `.planning/` milestone/phases.
 
 ## Compatibility
@@ -27,17 +31,19 @@ Run these checks and then present a compact table: `check | status | details | f
 ### Project state
 - `.planning/` exists (if missing, user hasn’t initialized a project).
 
+## Update check
+- Best-effort only; do not fail if offline.
 ### Update availability (best-effort)
 - Latest Codex fork version (do not fail if offline):
   - `npm view gsd-codex-cli version`
 - If installed Codex fork version is known and differs from latest, surface:
   - `Update available: {installed} -> {latest}`
-  - Next: `gsd-update` (Codex) / `/gsd:update` (Claude) or re-run `npx gsd-codex-cli@latest`.
+  - Next: `/prompts:gsd-update` (Codex) / `/gsd:update` (Claude) or re-run `npx gsd-codex-cli@latest`.
 
 ## Recommended fixes (use the minimum)
 - If engine missing: `npx gsd-codex-cli@latest --path .` (or `--global`)
 - If only Claude engine exists and Codex prompts are desired in-project: `npx gsd-codex-cli@latest --path .`
-- If `.planning/` missing: run `gsd-new-project` (Codex) / `/gsd:new-project` (Claude)
+- If `.planning/` missing: run `/prompts:gsd-new-project` (Codex) / `/gsd:new-project` (Claude)
 
 ## Completion output
 - Print the table and a single “Next recommended command”:

package/.codex/prompts/gsd-execute-phase.md

@@ -59,5 +59,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: `gsd-verify-work <phase>` (Codex) / `/gsd:verify-work <phase>` (Claude)
+- Next recommended command: `/prompts:gsd-verify-work <phase>` (Codex) / `/gsd:verify-work <phase>` (Claude)
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-help.md

@@ -30,12 +30,6 @@ Show available GSD commands and usage guide
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-insert-phase.md

@@ -30,12 +30,6 @@ Insert urgent work as decimal phase (for example 72.1) between existing phases
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse <after> <description> from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-list-phase-assumptions.md

@@ -30,12 +30,6 @@ Surface Claude's assumptions about a phase approach before planning
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[phase]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-map-codebase.md

@@ -30,12 +30,6 @@ Analyze codebase with parallel mapper agents to produce .planning/codebase/ docu
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[optional: specific area to map, for example api or auth]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-new-milestone.md

@@ -1,12 +1,12 @@
 ---
-description: Start a new milestone cycle — update PROJECT.md and route to requirements
+description: Start a new milestone cycle end-to-end (questioning -> requirements -> roadmap)
 argument-hint: "[milestone name, for example v1.1 Notifications]"
 ---
 
 $ARGUMENTS
 
 ## Objective
-Start a new milestone cycle — update PROJECT.md and route to requirements
+Start a new milestone cycle end-to-end (questioning -> requirements -> roadmap)
 
 ## Compatibility
 - Use .codex/skills/get-shit-done-codex semantics.
@@ -22,6 +22,8 @@ Start a new milestone cycle — update PROJECT.md and route to requirements
 - No jq / bash-only constructs.
 - Accept natural-language command input; do not require an exact literal argument template.
 - If a required argument is still missing after extraction, ask one concise clarification question.
+- If `.planning/MILESTONE-CONTEXT.md` is missing, ask options before drafting goals; do not assume milestone scope.
+- Do not complete successfully unless `.planning/ROADMAP.md` exists (or explicit `ROADMAP BLOCKED` is surfaced).
 
 ## Subagent lifecycle (required)
 
@@ -30,27 +32,28 @@ Start a new milestone cycle — update PROJECT.md and route to requirements
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[milestone name, for example v1.1 Notifications]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init new-milestone --raw
 
 3. Load .claude/get-shit-done/workflows/new-milestone.md and execute it step-by-step.
-4. Translate each Task(...) in workflow into:
+4. If `.planning/MILESTONE-CONTEXT.md` is absent, run an explicit options question before requirements:
+   - "Ship features (Recommended)"
+   - "Stabilize quality"
+   - "Platform + ops"
+   - "Custom scope"
+   Then summarize the chosen direction and ask for confirmation.
+5. Translate each Task(...) in workflow into:
    - spawn_agent with the matching role file context from .claude/agents/.
    - wait for each spawned agent and apply returned output before moving forward.
-5. Preserve all gates and routing from upstream workflow.
-6. Preserve commit behavior using 
+6. Preserve all gates and routing from upstream workflow.
+7. Before reporting success, verify `.planning/ROADMAP.md` exists. If missing, treat as blocked and continue workflow remediation.
+8. Preserve commit behavior using 
 node <gsd-tools-path> commit "message" --files ....
-7. If commit preflight fails (no git / no commit flag), proceed in read-only mode and report clearly.
+9. If commit preflight fails (no git / no commit flag), proceed in read-only mode and report clearly.
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-new-project.md

@@ -30,12 +30,6 @@ Initialize a new project with deep context gathering and PROJECT.md
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[--auto]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: `gsd-discuss-phase 1` (Codex) / `/gsd:discuss-phase 1` (Claude)
+- Next recommended command: `/prompts:gsd-discuss-phase 1` (Codex) / `/gsd:discuss-phase 1` (Claude)
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-pause-work.md

@@ -30,12 +30,6 @@ Create context handoff when pausing work mid-phase
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-plan-milestone-gaps.md

@@ -30,12 +30,6 @@ Create phases to close all gaps identified by milestone audit
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-plan-phase.md

@@ -30,12 +30,6 @@ Create detailed execution plan for a phase (PLAN.md) with verification loop
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[phase] [--research] [--skip-research] [--gaps] [--skip-verify]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: `gsd-execute-phase [phase]` (Codex) / `/gsd:execute-phase [phase]` (Claude)
+- Next recommended command: `/prompts:gsd-execute-phase [phase]` (Codex) / `/gsd:execute-phase [phase]` (Claude)
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-progress.md

@@ -30,12 +30,6 @@ Check project progress, show context, and route to next action
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-quick.md

@@ -30,12 +30,6 @@ Execute a quick task with GSD guarantees (atomic commits, state tracking) but sk
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-remove-phase.md

@@ -30,12 +30,6 @@ Remove a future phase from roadmap and renumber subsequent phases
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse <phase-number> from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-research-phase.md

@@ -30,12 +30,6 @@ Research how to implement a phase (standalone - usually use plan-phase instead)
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[phase]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-resume-work.md

@@ -30,12 +30,6 @@ Resume work from previous session with full context restoration
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-set-profile.md

@@ -30,12 +30,6 @@ Switch model profile for GSD agents (quality/balanced/budget)
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse <profile> from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-settings.md

@@ -30,12 +30,6 @@ Configure GSD workflow toggles and model profile
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-update.md

@@ -34,7 +34,7 @@ Update GSD to latest version with changelog display
 - Best-effort only; do not fail if offline.
 - Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
 - Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
+- If versions differ, surface: "Update available: <installed> -> <latest>. Next: /prompts:gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
 
 ## Execution
 1. No positional argument is required. Read flags from command text if present.
@@ -52,5 +52,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/prompts/gsd-verify-work.md

@@ -30,12 +30,6 @@ Validate built features through conversational UAT
 - Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
 - Do not advance workflow steps until wait and close complete.
 
-## Update check
-- Best-effort only; do not fail if offline.
-- Check installed Codex fork version from `.codex/gsd/VERSION` (or `~/.codex/gsd/VERSION`).
-- Check latest published version with `npm view gsd-codex-cli version`.
-- If versions differ, surface: "Update available: <installed> -> <latest>. Next: gsd-update (Codex) / /gsd:update (Claude) or re-run npx gsd-codex-cli@latest."
-
 ## Execution
 1. Parse "[phase number, for example 4]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
@@ -52,5 +46,5 @@ node <gsd-tools-path> commit "message" --files ....
 
 ## Completion output
 - Summarize key artifacts created/updated.
-- Next recommended command: use the next user-facing GSD command (Codex prompt name + Claude slash command).
+- Next recommended command: use the next user-facing GSD command (`/prompts:gsd-...` for Codex + `/gsd:...` for Claude).
 - Never recommend internal `node ... gsd-tools ...` commands to the user.

package/.codex/skills/get-shit-done-codex/SKILL.md

@@ -14,27 +14,27 @@ Use this skill to run `gsd-*` prompts under `Codex` while preserving upstream GS
 - Keep `.claude/agents/gsd-*.md` as role contracts for subagents.
 - Keep `.codex/prompts/gsd-*.md` as Codex-native orchestrators.
 
-## Core rules
-1. Do not change command semantics.
-2. Do not change source workflow logic unless necessary for Codex command compatibility.
-3. Use workspace-relative paths.
-4. Preserve step ordering and gate behavior from workflow files.
-5. User-facing guidance should recommend `gsd-*` prompts (Codex) and `/gsd:*` commands (Claude), not internal `node ... gsd-tools ...` plumbing.
+## Core rules
+1. Do not change command semantics.
+2. Do not change source workflow logic unless necessary for Codex command compatibility.
+3. Use workspace-relative paths.
+4. Preserve step ordering and gate behavior from workflow files.
+5. User-facing guidance should recommend `/prompts:gsd-*` prompts (Codex) and `/gsd:*` commands (Claude), not internal `node ... gsd-tools ...` plumbing.
 
 ## Mandatory codex translations
 - Replace each `Task(...)` with: `spawn_agent` + `wait`.
 - Replace Bash/JQ patterns with PowerShell and `ConvertFrom-Json`.
 - Replace AskUserQuestion interactions with direct user prompts in chat.
 
-## Subagent lifecycle (required)
-- Spawn only when the upstream workflow explicitly defines a `Task(...)` role.
-- For each spawned subagent:
-  - Start with `spawn_agent` and provide the role source from `.claude/agents/gsd-*.md`.
-  - Do not set `agent_type` to a GSD role. Codex only accepts `default`, `explorer`, or `worker` (or omit `agent_type`).
-  - Wait for completion before proceeding: `wait`.
-  - Explicitly close the agent after it finishes (`close_agent`) to release resources.
-- Keep prompt-level sequencing intact; do not continue to subsequent steps until waiting + closure are complete.
-- If an agent fails or exceeds retry policy, stop that phase of workflow and surface a clear remediation step.
+## Subagent lifecycle (required)
+- Spawn only when the upstream workflow explicitly defines a `Task(...)` role.
+- For each spawned subagent:
+  - Start with `spawn_agent` and provide the role source from `.claude/agents/gsd-*.md`.
+  - Do not set `agent_type` to a GSD role. Codex only accepts `default`, `explorer`, or `worker` (or omit `agent_type`).
+  - Wait for completion before proceeding: `wait`.
+  - Explicitly close the agent after it finishes (`close_agent`) to release resources.
+- Keep prompt-level sequencing intact; do not continue to subsequent steps until waiting + closure are complete.
+- If an agent fails or exceeds retry policy, stop that phase of workflow and surface a clear remediation step.
 
 ## Required GSD roles (must map by name)
 - `gsd-project-researcher`

package/README.md

@@ -34,11 +34,11 @@ This fork is Codex-first, but the Claude assets are kept alongside for compatibi
 
 ## Using the Prompts
 
-Open your project in Codex and run these prompts from the prompt list:
+Open your project in Codex and run these prompt commands:
 
-- `gsd-new-project`
-- `gsd-plan-phase`
-- `gsd-execute-phase`
+- `/prompts:gsd-new-project`
+- `/prompts:gsd-plan-phase`
+- `/prompts:gsd-execute-phase`
 
 All Codex prompts live in `.codex/prompts`.
 

package/bin/install-codex.js

@@ -11,18 +11,18 @@ const repoRoot = path.resolve(__dirname, '..');
 const helpText = `
 ${pkg.name} v${pkg.version}
 
-Usage:
-  ${pkg.name} [--path <target-dir>] [--help]
+Usage:
+  ${pkg.name} [--path <target-dir>] [--help]
 
 Options:
   --path <target-dir>   Install into this directory (defaults to current directory)
   --global              Also install .claude to your home directory (for manual sharing)
   --help, -h            Show this help message
 
-Examples:
-  npx gsd-codex-cli@latest --path .
-  npx gsd-codex-cli@latest --path ./my-project
-`;
+Examples:
+  npx gsd-codex-cli@latest --path .
+  npx gsd-codex-cli@latest --path ./my-project
+`;
 
 if (args.includes('--help') || args.includes('-h')) {
   console.log(helpText);
@@ -65,27 +65,27 @@ function resolveSourceDir(repoRelative, fallbackRelative) {
   throw new Error(`Missing source directory "${repoRelative}"${fallbackMessage} in repository root ${repoRoot}`);
 }
 
-function copyCodexToDirectory(baseDir) {
-  const targetCodex = path.join(baseDir, '.codex');
-  const targetClaude = path.join(baseDir, '.claude');
-  const sourceCodex = path.join(repoRoot, '.codex');
-  const sourceGetShitDone = resolveSourceDir('get-shit-done', '.claude/get-shit-done');
-  const sourceAgents = resolveSourceDir('agents', '.claude/agents');
-  const versionDest = path.join(targetClaude, 'get-shit-done', 'VERSION');
-  const codexVersionDest = path.join(targetCodex, 'gsd', 'VERSION');
-
-  ensureDir(baseDir);
-  ensureDir(targetCodex);
-  ensureDir(targetClaude);
-
-  copyRecursive(sourceCodex, targetCodex);
-  copyRecursive(sourceGetShitDone, path.join(targetClaude, 'get-shit-done'));
-  copyRecursive(sourceAgents, path.join(targetClaude, 'agents'));
-  ensureDir(path.dirname(versionDest));
-  fs.writeFileSync(versionDest, `${pkg.version}\n`);
-  ensureDir(path.dirname(codexVersionDest));
-  fs.writeFileSync(codexVersionDest, `${pkg.version}\n`);
-}
+function copyCodexToDirectory(baseDir) {
+  const targetCodex = path.join(baseDir, '.codex');
+  const targetClaude = path.join(baseDir, '.claude');
+  const sourceCodex = path.join(repoRoot, '.codex');
+  const sourceGetShitDone = resolveSourceDir('get-shit-done', '.claude/get-shit-done');
+  const sourceAgents = resolveSourceDir('agents', '.claude/agents');
+  const versionDest = path.join(targetClaude, 'get-shit-done', 'VERSION');
+  const codexVersionDest = path.join(targetCodex, 'gsd', 'VERSION');
+
+  ensureDir(baseDir);
+  ensureDir(targetCodex);
+  ensureDir(targetClaude);
+
+  copyRecursive(sourceCodex, targetCodex);
+  copyRecursive(sourceGetShitDone, path.join(targetClaude, 'get-shit-done'));
+  copyRecursive(sourceAgents, path.join(targetClaude, 'agents'));
+  ensureDir(path.dirname(versionDest));
+  fs.writeFileSync(versionDest, `${pkg.version}\n`);
+  ensureDir(path.dirname(codexVersionDest));
+  fs.writeFileSync(codexVersionDest, `${pkg.version}\n`);
+}
 
 copyCodexToDirectory(targetDir);
 
@@ -95,13 +95,13 @@ if (installGlobal) {
   copyCodexToDirectory(globalBase);
 }
 
-console.log(`\n${pkg.name}@${pkg.version} installed to:`);
+console.log(`\n${pkg.name}@${pkg.version} installed to:`);
 console.log(`  local: ${targetDir}`);
 if (installGlobal) {
   console.log('  global: ~/.codex');
 }
-console.log('\nNext steps:');
-console.log('  1) Open your project in Codex');
-console.log('  2) Run prompt gsd-new-project, then gsd-discuss-phase, gsd-plan-phase, gsd-execute-phase');
-console.log('  3) If something looks off, run prompt gsd-doctor');
-console.log('  4) Use .codex/prompts/* for all GSD commands in this fork');
+console.log('\nNext steps:');
+console.log('  1) Open your project in Codex');
+console.log('  2) Run /prompts:gsd-new-project, then /prompts:gsd-discuss-phase, /prompts:gsd-plan-phase, /prompts:gsd-execute-phase');
+console.log('  3) If something looks off, run /prompts:gsd-doctor');
+console.log('  4) Use .codex/prompts/* for all GSD commands in this fork');

package/commands/gsd/new-milestone.md

@@ -1,6 +1,6 @@
 ---
 name: gsd:new-milestone
-description: Start a new milestone cycle — update PROJECT.md and route to requirements
+description: Start a new milestone cycle end-to-end (questioning -> requirements -> roadmap)
 argument-hint: "[milestone name, e.g., 'v1.1 Notifications']"
 allowed-tools:
   - Read
@@ -48,4 +48,7 @@ Milestone name: $ARGUMENTS (optional - will prompt if not provided)
 <process>
 Execute the new-milestone workflow from @~/.claude/get-shit-done/workflows/new-milestone.md end-to-end.
 Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
+Hard gates:
+- If `.planning/MILESTONE-CONTEXT.md` is missing, present milestone direction options and capture user confirmation before defining requirements.
+- Do not finish successfully unless `.planning/ROADMAP.md` exists (or explicit blocked reason is reported).
 </process>

package/get-shit-done/workflows/new-milestone.md

@@ -26,9 +26,15 @@ Read all files referenced by the invoking prompt's execution_context before star
 - Present summary for confirmation
 
 **If no context file:**
-- Present what shipped in last milestone
-- Ask: "What do you want to build next?"
-- Use AskUserQuestion to explore features, priorities, constraints, scope
+- Present what shipped in last milestone plus pending todos/blockers.
+- Run an explicit AskUserQuestion with milestone direction options before drafting scope:
+  - "Ship features (Recommended)" — Build the next user-facing capability set
+  - "Stabilize quality" — Focus on bug fixes, reliability, and hardening
+  - "Platform + ops" — Improve architecture, performance, tooling, and observability
+  - "Custom scope" — User provides bespoke milestone goals
+- If "Custom scope", ask one focused follow-up question and capture the goals verbatim.
+- Summarize the selected direction as draft milestone goals and ask for confirm/adjust.
+- Hard gate: do not continue to Step 3 until user confirms goals.
 
 ## 3. Determine Milestone Version
 
@@ -319,6 +325,9 @@ Success criteria:
 **If "Adjust":** Get notes, re-spawn roadmapper with revision context, loop until approved.
 **If "Review":** Display raw ROADMAP.md, re-ask.
 
+**Hard gate before completion:** verify `.planning/ROADMAP.md` exists on disk.
+- If missing, treat as `## ROADMAP BLOCKED` (agent returned success without writing file), explain the issue, and re-spawn roadmapper with explicit instruction to write `.planning/ROADMAP.md`, `.planning/STATE.md`, and REQUIREMENTS traceability updates before returning.
+
 **Commit roadmap** (after approval):
 ```bash
 node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs: create milestone v[X.Y] roadmap ([N] phases)" --files .planning/ROADMAP.md .planning/STATE.md .planning/REQUIREMENTS.md
@@ -364,6 +373,7 @@ Also: `/gsd:plan-phase [N]` — skip discussion, plan directly
 - [ ] REQUIREMENTS.md created with REQ-IDs
 - [ ] gsd-roadmapper spawned with phase numbering context
 - [ ] Roadmap files written immediately (not draft)
+- [ ] `.planning/ROADMAP.md` exists on disk before Done
 - [ ] User feedback incorporated (if any)
 - [ ] ROADMAP.md phases continue from previous milestone
 - [ ] All commits made (if planning docs committed)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "gsd-codex-cli",
-  "version": "1.20.9",
+  "version": "1.20.11",
   "description": "Codex-native package for the get-shit-done workflow with native subagent orchestration.",
   "bin": {
     "gsd-codex-cli": "bin/install-codex.js",