@undeemed/get-shit-done-codex 1.6.12 → 1.20.3

package/commands/gsd/remove-phase.md

@@ -8,7 +8,6 @@ allowed-tools:
   - Bash
   - Glob
 ---
-
 <objective>
 Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
 
@@ -17,322 +16,17 @@ Output: Phase deleted, all subsequent phases renumbered, git commit as historica
 </objective>
 
 <execution_context>
-@.planning/ROADMAP.md
-@.planning/STATE.md
+@~/.codex/get-shit-done/workflows/remove-phase.md
 </execution_context>
 
-<process>
-
-<step name="parse_arguments">
-Parse the command arguments:
-- Argument is the phase number to remove (integer or decimal)
-- Example: `/gsd:remove-phase 17` → phase = 17
-- Example: `/gsd:remove-phase 16.1` → phase = 16.1
-
-If no argument provided:
-
-```
-ERROR: Phase number required
-Usage: /gsd:remove-phase <phase-number>
-Example: /gsd:remove-phase 17
-```
-
-Exit.
-</step>
-
-<step name="load_state">
-Load project state:
-
-```bash
-cat .planning/STATE.md 2>/dev/null
-cat .planning/ROADMAP.md 2>/dev/null
-```
-
-Parse current phase number from STATE.md "Current Position" section.
-</step>
-
-<step name="validate_phase_exists">
-Verify the target phase exists in ROADMAP.md:
-
-1. Search for `### Phase {target}:` heading
-2. If not found:
-
-   ```
-   ERROR: Phase {target} not found in roadmap
-   Available phases: [list phase numbers]
-   ```
-
-   Exit.
-</step>
-
-<step name="validate_future_phase">
-Verify the phase is a future phase (not started):
-
-1. Compare target phase to current phase from STATE.md
-2. Target must be > current phase number
-
-If target <= current phase:
-
-```
-ERROR: Cannot remove Phase {target}
-
-Only future phases can be removed:
-- Current phase: {current}
-- Phase {target} is current or completed
-
-To abandon current work, use /gsd:pause-work instead.
-```
-
-Exit.
-
-3. Check for SUMMARY.md files in phase directory:
-
-```bash
-ls .planning/phases/{target}-*/*-SUMMARY.md 2>/dev/null
-```
-
-If any SUMMARY.md files exist:
-
-```
-ERROR: Phase {target} has completed work
-
-Found executed plans:
-- {list of SUMMARY.md files}
-
-Cannot remove phases with completed work.
-```
-
-Exit.
-</step>
-
-<step name="gather_phase_info">
-Collect information about the phase being removed:
-
-1. Extract phase name from ROADMAP.md heading: `### Phase {target}: {Name}`
-2. Find phase directory: `.planning/phases/{target}-{slug}/`
-3. Find all subsequent phases (integer and decimal) that need renumbering
-
-**Subsequent phase detection:**
-
-For integer phase removal (e.g., 17):
-- Find all phases > 17 (integers: 18, 19, 20...)
-- Find all decimal phases >= 17.0 and < 18.0 (17.1, 17.2...) → these become 16.x
-- Find all decimal phases for subsequent integers (18.1, 19.1...) → renumber with their parent
-
-For decimal phase removal (e.g., 17.1):
-- Find all decimal phases > 17.1 and < 18 (17.2, 17.3...) → renumber down
-- Integer phases unchanged
-
-List all phases that will be renumbered.
-</step>
-
-<step name="confirm_removal">
-Present removal summary and confirm:
-
-```
-Removing Phase {target}: {Name}
-
-This will:
-- Delete: .planning/phases/{target}-{slug}/
-- Renumber {N} subsequent phases:
-  - Phase 18 → Phase 17
-  - Phase 18.1 → Phase 17.1
-  - Phase 19 → Phase 18
-  [etc.]
-
-Proceed? (y/n)
-```
-
-Wait for confirmation.
-</step>
-
-<step name="delete_phase_directory">
-Delete the target phase directory if it exists:
-
-```bash
-if [ -d ".planning/phases/{target}-{slug}" ]; then
-  rm -rf ".planning/phases/{target}-{slug}"
-  echo "Deleted: .planning/phases/{target}-{slug}/"
-fi
-```
-
-If directory doesn't exist, note: "No directory to delete (phase not yet created)"
-</step>
-
-<step name="renumber_directories">
-Rename all subsequent phase directories:
-
-For each phase directory that needs renumbering (in reverse order to avoid conflicts):
-
-```bash
-# Example: renaming 18-dashboard to 17-dashboard
-mv ".planning/phases/18-dashboard" ".planning/phases/17-dashboard"
-```
-
-Process in descending order (20→19, then 19→18, then 18→17) to avoid overwriting.
+<context>
+Phase: $ARGUMENTS
 
-Also rename decimal phase directories:
-- `17.1-fix-bug` → `16.1-fix-bug` (if removing integer 17)
-- `17.2-hotfix` → `17.1-hotfix` (if removing decimal 17.1)
-</step>
-
-<step name="rename_files_in_directories">
-Rename plan files inside renumbered directories:
-
-For each renumbered directory, rename files that contain the phase number:
-
-```bash
-# Inside 17-dashboard (was 18-dashboard):
-mv "18-01-PLAN.md" "17-01-PLAN.md"
-mv "18-02-PLAN.md" "17-02-PLAN.md"
-mv "18-01-SUMMARY.md" "17-01-SUMMARY.md"  # if exists
-# etc.
-```
-
-Also handle CONTEXT.md and DISCOVERY.md (these don't have phase prefixes, so no rename needed).
-</step>
-
-<step name="update_roadmap">
-Update ROADMAP.md:
-
-1. **Remove the phase section entirely:**
-   - Delete from `### Phase {target}:` to the next phase heading (or section end)
-
-2. **Remove from phase list:**
-   - Delete line `- [ ] **Phase {target}: {Name}**` or similar
-
-3. **Remove from Progress table:**
-   - Delete the row for Phase {target}
-
-4. **Renumber all subsequent phases:**
-   - `### Phase 18:` → `### Phase 17:`
-   - `- [ ] **Phase 18:` → `- [ ] **Phase 17:`
-   - Table rows: `| 18. Dashboard |` → `| 17. Dashboard |`
-   - Plan references: `18-01:` → `17-01:`
-
-5. **Update dependency references:**
-   - `**Depends on:** Phase 18` → `**Depends on:** Phase 17`
-   - For the phase that depended on the removed phase:
-     - `**Depends on:** Phase 17` (removed) → `**Depends on:** Phase 16`
-
-6. **Renumber decimal phases:**
-   - `### Phase 17.1:` → `### Phase 16.1:` (if integer 17 removed)
-   - Update all references consistently
-
-Write updated ROADMAP.md.
-</step>
-
-<step name="update_state">
-Update STATE.md:
-
-1. **Update total phase count:**
-   - `Phase: 16 of 20` → `Phase: 16 of 19`
-
-2. **Recalculate progress percentage:**
-   - New percentage based on completed plans / new total plans
-
-Do NOT add a "Roadmap Evolution" note - the git commit is the record.
-
-Write updated STATE.md.
-</step>
-
-<step name="update_file_contents">
-Search for and update phase references inside plan files:
-
-```bash
-# Find files that reference the old phase numbers
-grep -r "Phase 18" .planning/phases/17-*/ 2>/dev/null
-grep -r "Phase 19" .planning/phases/18-*/ 2>/dev/null
-# etc.
-```
-
-Update any internal references to reflect new numbering.
-</step>
-
-<step name="commit">
-Stage and commit the removal:
-
-```bash
-git add .planning/
-git commit -m "chore: remove phase {target} ({original-phase-name})"
-```
-
-The commit message preserves the historical record of what was removed.
-</step>
-
-<step name="completion">
-Present completion summary:
-
-```
-Phase {target} ({original-name}) removed.
-
-Changes:
-- Deleted: .planning/phases/{target}-{slug}/
-- Renumbered: Phases {first-renumbered}-{last-old} → {first-renumbered-1}-{last-new}
-- Updated: ROADMAP.md, STATE.md
-- Committed: chore: remove phase {target} ({original-name})
-
-Current roadmap: {total-remaining} phases
-Current position: Phase {current} of {new-total}
-
----
-
-## What's Next
-
-Would you like to:
-- `/gsd:progress` — see updated roadmap status
-- Continue with current phase
-- Review roadmap
-
----
-```
-</step>
+@.planning/ROADMAP.md
+@.planning/STATE.md
+</context>
 
+<process>
+Execute the remove-phase workflow from @~/.codex/get-shit-done/workflows/remove-phase.md end-to-end.
+Preserve all validation gates (future phase check, work check), renumbering logic, and commit.
 </process>
-
-<anti_patterns>
-
-- Don't remove completed phases (have SUMMARY.md files)
-- Don't remove current or past phases
-- Don't leave gaps in numbering - always renumber
-- Don't add "removed phase" notes to STATE.md - git commit is the record
-- Don't ask about each decimal phase - just renumber them
-- Don't modify completed phase directories
-</anti_patterns>
-
-<edge_cases>
-
-**Removing a decimal phase (e.g., 17.1):**
-- Only affects other decimals in same series (17.2 → 17.1, 17.3 → 17.2)
-- Integer phases unchanged
-- Simpler operation
-
-**No subsequent phases to renumber:**
-- Removing the last phase (e.g., Phase 20 when that's the end)
-- Just delete and update ROADMAP.md, no renumbering needed
-
-**Phase directory doesn't exist:**
-- Phase may be in ROADMAP.md but directory not created yet
-- Skip directory deletion, proceed with ROADMAP.md updates
-
-**Decimal phases under removed integer:**
-- Removing Phase 17 when 17.1, 17.2 exist
-- 17.1 → 16.1, 17.2 → 16.2
-- They maintain their position in execution order (after current last integer)
-
-</edge_cases>
-
-<success_criteria>
-Phase removal is complete when:
-
-- [ ] Target phase validated as future/unstarted
-- [ ] Phase directory deleted (if existed)
-- [ ] All subsequent phase directories renumbered
-- [ ] Files inside directories renamed ({old}-01-PLAN.md → {new}-01-PLAN.md)
-- [ ] ROADMAP.md updated (section removed, all references renumbered)
-- [ ] STATE.md updated (phase count, progress percentage)
-- [ ] Dependency references updated in subsequent phases
-- [ ] Changes committed with descriptive message
-- [ ] No gaps in phase numbering
-- [ ] User informed of changes
-</success_criteria>

package/commands/gsd/research-phase.md

@@ -31,22 +31,26 @@ Normalize phase input in step 1 before any directory lookups.
 
 <process>
 
-## 1. Normalize and Validate Phase
+## 0. Initialize Context
 
 ```bash
-# Normalize phase number (8 → 08, but preserve decimals like 2.1 → 02.1)
-if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
-  PHASE=$(printf "%02d" "$ARGUMENTS")
-elif [[ "$ARGUMENTS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
-  PHASE=$(printf "%02d.%s" "${BASH_REMATCH[1]}" "${BASH_REMATCH[2]}")
-else
-  PHASE="$ARGUMENTS"
-fi
-
-grep -A5 "Phase ${PHASE}:" .planning/ROADMAP.md 2>/dev/null
+INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init phase-op "$ARGUMENTS")
 ```
 
-**If not found:** Error and exit. **If found:** Extract phase number, name, description.
+Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`.
+
+Resolve researcher model:
+```bash
+RESEARCHER_MODEL=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs resolve-model gsd-phase-researcher --raw)
+```
+
+## 1. Validate Phase
+
+```bash
+PHASE_INFO=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs roadmap get-phase "${phase_number}")
+```
+
+**If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.
 
 ## 2. Check Existing Research
 
@@ -61,15 +65,16 @@ ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
 ## 3. Gather Phase Context
 
 ```bash
-grep -A20 "Phase ${PHASE}:" .planning/ROADMAP.md
+# Phase section already loaded in PHASE_INFO
+echo "$PHASE_INFO" | jq -r '.section'
 cat .planning/REQUIREMENTS.md 2>/dev/null
-cat .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
+cat .planning/phases/${PHASE}-*/*-CONTEXT.md 2>/dev/null
 grep -A30 "### Decisions Made" .planning/STATE.md 2>/dev/null
 ```
 
 Present summary with phase description, requirements, prior decisions.
 
-## 4. Spawn gsd-researcher Agent
+## 4. Spawn gsd-phase-researcher Agent
 
 Research modes: ecosystem (default), feasibility, implementation, comparison.
 
@@ -87,7 +92,7 @@ For this phase, discover:
 - What's the established architecture pattern?
 - What libraries form the standard stack?
 - What problems do people commonly hit?
-- What's SOTA vs what Claude's training thinks is SOTA?
+- What's SOTA vs what Codex's training thinks is SOTA?
 - What should NOT be hand-rolled?
 </key_insight>
 
@@ -130,8 +135,9 @@ Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
 
 ```
 Task(
-  prompt=filled_prompt,
-  subagent_type="gsd-phase-researcher",
+  prompt="First, read ~/.codex/agents/gsd-phase-researcher.md for your role and instructions.\n\n" + filled_prompt,
+  subagent_type="general-purpose",
+  model="{researcher_model}",
   description="Research Phase {phase}"
 )
 ```
@@ -163,8 +169,9 @@ Research file: @.planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
 
 ```
 Task(
-  prompt=continuation_prompt,
-  subagent_type="gsd-phase-researcher",
+  prompt="First, read ~/.codex/agents/gsd-phase-researcher.md for your role and instructions.\n\n" + continuation_prompt,
+  subagent_type="general-purpose",
+  model="{researcher_model}",
   description="Continue research Phase {phase}"
 )
 ```

package/commands/gsd/resume-work.md

@@ -22,11 +22,11 @@ Routes to the resume-project workflow which handles:
   </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/resume-project.md
+@~/.codex/get-shit-done/workflows/resume-project.md
 </execution_context>
 
 <process>
-**Follow the resume-project workflow** from `@~/.claude/get-shit-done/workflows/resume-project.md`.
+**Follow the resume-project workflow** from `@~/.codex/get-shit-done/workflows/resume-project.md`.
 
 The workflow handles all resumption logic including:
 

package/commands/gsd/set-profile.md

@@ -0,0 +1,34 @@
+---
+name: gsd:set-profile
+description: Switch model profile for GSD agents (quality/balanced/budget)
+argument-hint: <profile>
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+<objective>
+Switch the model profile used by GSD agents. Controls which Codex model each agent uses, balancing quality vs token spend.
+
+Routes to the set-profile workflow which handles:
+- Argument validation (quality/balanced/budget)
+- Config file creation if missing
+- Profile update in config.json
+- Confirmation with model table display
+</objective>
+
+<execution_context>
+@~/.codex/get-shit-done/workflows/set-profile.md
+</execution_context>
+
+<process>
+**Follow the set-profile workflow** from `@~/.codex/get-shit-done/workflows/set-profile.md`.
+
+The workflow handles all logic including:
+1. Profile argument validation
+2. Config file ensuring
+3. Config reading and updating
+4. Model table generation from MODEL_PROFILES
+5. Confirmation display
+</process>

package/commands/gsd/settings.md

@@ -0,0 +1,36 @@
+---
+name: gsd:settings
+description: Configure GSD workflow toggles and model profile
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
+---
+
+<objective>
+Interactive configuration of GSD workflow agents and model profile via multi-question prompt.
+
+Routes to the settings workflow which handles:
+- Config existence ensuring
+- Current settings reading and parsing
+- Interactive 5-question prompt (model, research, plan_check, verifier, branching)
+- Config merging and writing
+- Confirmation display with quick command references
+</objective>
+
+<execution_context>
+@~/.codex/get-shit-done/workflows/settings.md
+</execution_context>
+
+<process>
+**Follow the settings workflow** from `@~/.codex/get-shit-done/workflows/settings.md`.
+
+The workflow handles all logic including:
+1. Config file creation with defaults if missing
+2. Current config reading
+3. Interactive settings presentation with pre-selection
+4. Answer parsing and config merging
+5. File writing
+6. Confirmation display
+</process>