gsd-codex-cli 1.20.7 → 1.20.9

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

@@ -3,6 +3,8 @@ description: Add phase to end of current milestone in roadmap
 argument-hint: <description>
 ---
 
+$ARGUMENTS
+
 ## Objective
 Add phase to end of current milestone in roadmap
 
@@ -15,9 +17,11 @@ Add phase to end of current milestone in roadmap
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Add phase to end of current milestone in roadmap
 - 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 the user input.
+1. Parse <description> from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op "0" --raw
 

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

@@ -3,6 +3,8 @@ description: Capture idea or task as todo from current conversation context
 argument-hint: [optional description]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Capture idea or task as todo from current conversation context
 
@@ -15,9 +17,11 @@ Capture idea or task as todo from current conversation context
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Capture idea or task as todo from current conversation context
 - 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 the user input.
+1. Parse [optional description] from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init todos [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Audit milestone completion against original intent before archiving
 argument-hint: "[version]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Audit milestone completion against original intent before archiving
 
@@ -15,9 +17,11 @@ Audit milestone completion against original intent before archiving
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Audit milestone completion against original intent before archiving
 - 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 the user input.
+1. Parse "[version]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init milestone-op --raw
 

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

@@ -3,6 +3,8 @@ description: List pending todos and select one to work on
 argument-hint: [area filter]
 ---
 
+$ARGUMENTS
+
 ## Objective
 List pending todos and select one to work on
 
@@ -15,9 +17,11 @@ List pending todos and select one to work on
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ List pending todos and select one to work on
 - 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 the user input.
+1. Parse [area filter] from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init todos [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Archive completed milestone and prepare for next version
 argument-hint: <version>
 ---
 
+$ARGUMENTS
+
 ## Objective
 Archive completed milestone and prepare for next version
 
@@ -15,9 +17,11 @@ Archive completed milestone and prepare for next version
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Archive completed milestone and prepare for next 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 the user input.
+1. Parse <version> from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init execute-phase "1" --raw
 

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

@@ -3,6 +3,8 @@ description: Systematic debugging with persistent state across context resets
 argument-hint: [issue description]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Systematic debugging with persistent state across context resets
 
@@ -15,9 +17,11 @@ Systematic debugging with persistent state across context resets
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Systematic debugging with persistent state across context resets
 - 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 the user input.
+1. Parse [issue description] from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> state load --raw
 

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

@@ -3,6 +3,8 @@ description: Gather phase context through adaptive questioning before planning
 argument-hint: "<phase>"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Gather phase context through adaptive questioning before planning
 
@@ -15,9 +17,11 @@ Gather phase context through adaptive questioning before planning
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Gather phase context through adaptive questioning before planning
 - 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 the user input.
+1. Parse "<phase>" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Execute all plans in a phase with wave-based parallelization
 argument-hint: "<phase-number> [--gaps-only]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Execute all plans in a phase with wave-based parallelization
 
@@ -13,42 +15,49 @@ Execute all plans in a phase with wave-based parallelization
 - Use one of these engine paths (prefer local, fallback global):
   node .claude/get-shit-done/bin/gsd-tools.js ...
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
-- If `.js` is unavailable, use the same path with `.cjs`.
-- Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
-- Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
-- No jq / bash-only constructs.
-
-## Subagent lifecycle (required)
-
-- Translate each upstream `Task(...)` into `spawn_agent` -> `wait` -> `close_agent`.
-- Spawn only when the upstream workflow defines an agent role.
-- Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
-- Do not advance workflow steps until wait and close complete.
-
-## Input contract
-- The command argument is authoritative.
-- If user runs `gsd-execute-phase 28`, execute phase `28`. Do not auto-discover a different phase.
-- Parse flags only from the same argument string (`--gaps-only`, `--auto`).
-- If phase argument is missing or invalid, stop and ask for a valid phase number.
-
-## Execution
-1. Parse "<phase-number> [--gaps-only] [--auto]" from the command argument string.
-2. Treat parsed phase as the execution target and keep it unchanged for all downstream steps.
-3. Run init with the parsed phase:
-node <gsd-tools-path> init execute-phase <phase> --raw
-4. If `--gaps-only` is present, apply gap-closure filtering exactly as defined in the upstream workflow.
-5. If `--auto` is present, preserve auto-advance behavior from the upstream workflow.
-6. Load .claude/get-shit-done/workflows/execute-phase.md and execute it step-by-step.
-7. 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.
-8. Preserve all gates and routing from upstream workflow.
-9. Preserve commit behavior using
-node <gsd-tools-path> commit "message" --files ....
-10. 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: `gsd-verify-work <phase>` (Codex) / `/gsd:verify-work <phase>` (Claude)
-- Never recommend internal `node ... gsd-tools ...` commands to the user.
+- If `.js` is unavailable, use the same path with `.cjs`.
+- Run engine commands through PowerShell.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
+- Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
+- 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.
+
+## Subagent lifecycle (required)
+
+- Translate each upstream `Task(...)` into `spawn_agent` -> `wait` -> `close_agent`.
+- Spawn only when the upstream workflow defines an agent role.
+- Use `.claude/agents/gsd-*.md` as role context for each spawned agent.
+- Do not advance workflow steps until wait and close complete.
+
+## Input contract
+- The command argument is authoritative.
+- If user runs `gsd-execute-phase 28`, execute phase `28`. Do not auto-discover a different phase.
+- Parse phase from either:
+  - the explicit command argument tail, or
+  - the latest user message (for example: "execute phase 28").
+- Accept the first numeric token as phase number (integer or decimal, e.g., 30 or 30.1).
+- Parse flags `--gaps-only` and `--auto` from the same input text when present.
+- Do not claim "phase missing" when the latest user input already contains a valid phase token.
+- Only ask for input if no valid phase token is found anywhere in the latest user request.
+
+## Execution
+1. Parse "<phase-number> [--gaps-only] [--auto]" from command argument text, or extract from the latest user message.
+2. Treat parsed phase as the execution target and keep it unchanged for all downstream steps.
+3. Run init with the parsed phase:
+node <gsd-tools-path> init execute-phase <phase> --raw
+4. If `--gaps-only` is present, apply gap-closure filtering exactly as defined in the upstream workflow.
+5. If `--auto` is present, preserve auto-advance behavior from the upstream workflow.
+6. Load .claude/get-shit-done/workflows/execute-phase.md and execute it step-by-step.
+7. 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.
+8. Preserve all gates and routing from upstream workflow.
+9. Preserve commit behavior using
+node <gsd-tools-path> commit "message" --files ....
+10. 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: `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

@@ -3,6 +3,8 @@ description: Show available GSD commands and usage guide
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Show available GSD commands and usage guide
 
@@ -15,9 +17,11 @@ Show available GSD commands and usage guide
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Show available GSD commands and usage guide
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 # No explicit init.
 

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

@@ -3,6 +3,8 @@ description: Insert urgent work as decimal phase (for example 72.1) between exis
 argument-hint: <after> <description>
 ---
 
+$ARGUMENTS
+
 ## Objective
 Insert urgent work as decimal phase (for example 72.1) between existing phases
 
@@ -15,9 +17,11 @@ Insert urgent work as decimal phase (for example 72.1) between existing phases
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Insert urgent work as decimal phase (for example 72.1) between existing phases
 - 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 the user input.
+1. Parse <after> <description> from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op [after-phase] --raw
 

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

@@ -3,6 +3,8 @@ description: Surface Claude's assumptions about a phase approach before planning
 argument-hint: "[phase]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Surface Claude's assumptions about a phase approach before planning
 
@@ -15,9 +17,11 @@ Surface Claude's assumptions about a phase approach before planning
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Surface Claude's assumptions about a phase approach before planning
 - 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 the user input.
+1. Parse "[phase]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Analyze codebase with parallel mapper agents to produce .planning/c
 argument-hint: "[optional: specific area to map, for example api or auth]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
 
@@ -15,9 +17,11 @@ Analyze codebase with parallel mapper agents to produce .planning/codebase/ docu
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Analyze codebase with parallel mapper agents to produce .planning/codebase/ docu
 - 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 the user input.
+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:
 node <gsd-tools-path> init map-codebase --raw
 

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

@@ -3,6 +3,8 @@ description: Start a new milestone cycle — update PROJECT.md and route to requ
 argument-hint: "[milestone name, for example v1.1 Notifications]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Start a new milestone cycle — update PROJECT.md and route to requirements
 
@@ -15,9 +17,11 @@ Start a new milestone cycle — update PROJECT.md and route to requirements
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Start a new milestone cycle — update PROJECT.md and route to requirements
 - 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 the user input.
+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
 

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

@@ -3,6 +3,8 @@ description: Initialize a new project with deep context gathering and PROJECT.md
 argument-hint: "[--auto]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Initialize a new project with deep context gathering and PROJECT.md
 
@@ -15,9 +17,11 @@ Initialize a new project with deep context gathering and PROJECT.md
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Initialize a new project with deep context gathering and PROJECT.md
 - 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 the user input.
+1. Parse "[--auto]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init new-project --raw
 

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

@@ -3,6 +3,8 @@ description: Create context handoff when pausing work mid-phase
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Create context handoff when pausing work mid-phase
 
@@ -15,9 +17,11 @@ Create context handoff when pausing work mid-phase
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Create context handoff when pausing work mid-phase
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> state load --raw
 

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

@@ -3,6 +3,8 @@ description: Create phases to close all gaps identified by milestone audit
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Create phases to close all gaps identified by milestone audit
 
@@ -15,9 +17,11 @@ Create phases to close all gaps identified by milestone audit
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Create phases to close all gaps identified by milestone audit
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> init milestone-op --raw
 

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

@@ -3,6 +3,8 @@ description: Create detailed execution plan for a phase (PLAN.md) with verificat
 argument-hint: "[phase] [--research] [--skip-research] [--gaps] [--skip-verify]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Create detailed execution plan for a phase (PLAN.md) with verification loop
 
@@ -15,9 +17,11 @@ Create detailed execution plan for a phase (PLAN.md) with verification loop
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Create detailed execution plan for a phase (PLAN.md) with verification loop
 - 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 the user input.
+1. Parse "[phase] [--research] [--skip-research] [--gaps] [--skip-verify]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init plan-phase [phase] --include state,roadmap,requirements,context,research,verification,uat --raw
 

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

@@ -3,6 +3,8 @@ description: Check project progress, show context, and route to next action
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Check project progress, show context, and route to next action
 
@@ -15,9 +17,11 @@ Check project progress, show context, and route to next action
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Check project progress, show context, and route to next action
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> init progress --include state,roadmap,project,config --raw
 

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

@@ -3,6 +3,8 @@ description: Execute a quick task with GSD guarantees (atomic commits, state tra
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents
 
@@ -15,9 +17,11 @@ Execute a quick task with GSD guarantees (atomic commits, state tracking) but sk
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Execute a quick task with GSD guarantees (atomic commits, state tracking) but sk
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> init quick "[argument]" --raw
 

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

@@ -3,6 +3,8 @@ description: Remove a future phase from roadmap and renumber subsequent phases
 argument-hint: <phase-number>
 ---
 
+$ARGUMENTS
+
 ## Objective
 Remove a future phase from roadmap and renumber subsequent phases
 
@@ -15,9 +17,11 @@ Remove a future phase from roadmap and renumber subsequent phases
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Remove a future phase from roadmap and renumber subsequent phases
 - 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 the user input.
+1. Parse <phase-number> from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Research how to implement a phase (standalone - usually use plan-ph
 argument-hint: "[phase]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Research how to implement a phase (standalone - usually use plan-phase instead)
 
@@ -15,9 +17,11 @@ Research how to implement a phase (standalone - usually use plan-phase instead)
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Research how to implement a phase (standalone - usually use plan-phase instead)
 - 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 the user input.
+1. Parse "[phase]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init phase-op [argument] --raw
 

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

@@ -3,6 +3,8 @@ description: Resume work from previous session with full context restoration
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Resume work from previous session with full context restoration
 
@@ -15,9 +17,11 @@ Resume work from previous session with full context restoration
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Resume work from previous session with full context restoration
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> init resume --raw
 

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

@@ -3,6 +3,8 @@ description: Switch model profile for GSD agents (quality/balanced/budget)
 argument-hint: <profile>
 ---
 
+$ARGUMENTS
+
 ## Objective
 Switch model profile for GSD agents (quality/balanced/budget)
 
@@ -15,9 +17,11 @@ Switch model profile for GSD agents (quality/balanced/budget)
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Switch model profile for GSD agents (quality/balanced/budget)
 - 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 the user input.
+1. Parse <profile> from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> state load --raw
 

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

@@ -3,6 +3,8 @@ description: Configure GSD workflow toggles and model profile
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Configure GSD workflow toggles and model profile
 
@@ -15,9 +17,11 @@ Configure GSD workflow toggles and model profile
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Configure GSD workflow toggles and model profile
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 node <gsd-tools-path> config-ensure-section --raw
 

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

@@ -3,6 +3,8 @@ description: Update GSD to latest version with changelog display
 argument-hint: [none]
 ---
 
+$ARGUMENTS
+
 ## Objective
 Update GSD to latest version with changelog display
 
@@ -15,9 +17,11 @@ Update GSD to latest version with changelog display
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Update GSD to latest version with changelog display
 - 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 [none] from the user input.
+1. No positional argument is required. Read flags from command text if present.
 2. Run init:
 # No explicit init.
 

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

@@ -3,6 +3,8 @@ description: Validate built features through conversational UAT
 argument-hint: "[phase number, for example 4]"
 ---
 
+$ARGUMENTS
+
 ## Objective
 Validate built features through conversational UAT
 
@@ -15,9 +17,11 @@ Validate built features through conversational UAT
   node ~/.claude/get-shit-done/bin/gsd-tools.js ...
 - If `.js` is unavailable, use the same path with `.cjs`.
 - Run engine commands through PowerShell.
-- Do not set `node <path> ...` as one string variable and invoke `& $var`; run direct `node <path> ...` or `& node <path> ...`.
+- Do not set `node <path> ...` as one string variable and invoke `& <cmd_var>`; run direct `node <path> ...` or `& node <path> ...`.
 - Parse JSON with ConvertFrom-Json; parse key/value output when workflow uses KEY=value raw mode.
 - 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.
 
 ## Subagent lifecycle (required)
 
@@ -33,7 +37,7 @@ Validate built features through conversational UAT
 - 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 the user input.
+1. Parse "[phase number, for example 4]" from command argument text or the latest user message (natural language allowed).
 2. Run init:
 node <gsd-tools-path> init verify-work [phase] --raw
 

package/package.json

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