@undeemed/get-shit-done-codex 1.20.2 → 1.20.7

package/README.md

@@ -19,7 +19,7 @@ get-shit-done-codex (GSD) solves context rot — the quality degradation that ha
 ## Installation
 
 ```bash
-npx @undeemed/get-shit-done-codex
+npx @undeemed/get-shit-done-codex@latest
 ```
 
 You'll be prompted to install globally (`~/.codex/`) or locally (`./`).
@@ -45,6 +45,20 @@ npx @undeemed/get-shit-done-codex@latest --global
 
 The installer now writes a `get-shit-done/VERSION` file so `/prompts:gsd-update` can detect installed vs latest and show changelog before updating.
 
+## npm Trusted Publisher (OIDC)
+
+This repo includes a GitHub Actions publish workflow at:
+
+- `.github/workflows/publish.yml`
+
+When setting up npm Trusted Publisher for this package, use:
+
+- **Publisher:** `GitHub Actions`
+- **Organization or user:** `undeemed`
+- **Repository:** `get-shit-done-codex`
+- **Workflow filename:** `publish.yml`
+- **Environment name:** leave blank (unless you later bind this workflow to a specific GitHub Environment)
+
 ## Quick Start
 
 ```bash
@@ -70,6 +84,7 @@ The installer now writes a `get-shit-done/VERSION` file so `/prompts:gsd-update`
 ```
 
 One command takes you from idea to ready-for-planning:
+
 - Deep questioning to understand what you're building
 - Optional domain research (spawns 4 parallel researcher agents)
 - Requirements definition with v1/v2/out-of-scope scoping
@@ -108,7 +123,7 @@ Manual user acceptance testing. The system walks you through testable deliverabl
 ## Commands
 
 | Command                             | Description                                                       |
-|-------------------------------------|-------------------------------------------------------------------|
+| ----------------------------------- | ----------------------------------------------------------------- |
 | `/prompts:gsd-new-project`          | Initialize project: questions → research → requirements → roadmap |
 | `/prompts:gsd-plan-phase [N]`       | Research + plan + verify for a phase                              |
 | `/prompts:gsd-execute-phase <N>`    | Execute all plans in parallel waves                               |
@@ -160,15 +175,18 @@ Git bisect finds exact failing task. Each task independently revertable.
 ## Troubleshooting
 
 **Commands not found?**
+
 - Restart Codex CLI to reload prompts
 - Check `~/.codex/prompts/gsd-*.md` (global) or `./prompts/gsd-*.md` (local)
 
 **Update to latest:**
+
 ```bash
 npx @undeemed/get-shit-done-codex@latest
 ```
 
 **Can users be notified when an update is available?**
+
 - Yes. The installer prints an update notice if a newer npm version exists.
 - In-Codex update checks are available via `/prompts:gsd-update`.
 - For release notifications outside the CLI, enable GitHub release watching on this repo.
@@ -178,16 +196,22 @@ npx @undeemed/get-shit-done-codex@latest
 For deeper guides, detailed workflows, and comprehensive documentation, see the [original get-shit-done README](https://github.com/taches/get-shit-done/blob/main/README.md).
 
 The original repository contains:
+
 - Detailed workflow explanations
 - Advanced usage patterns
 - Complete command reference
 - Best practices and examples
 - Architecture and design principles
 
-**Note:** The original README is written for Claude Code. When following it, remember that this fork uses:
+**Note:** The original README is written for Codex Code. When following it, remember that this fork uses:
+
 - `/prompts:gsd-*` command format (instead of `/gsd:*`)
-- Codex CLI (instead of Claude Code)
-- `~/.codex/` directory (instead of `~/.claude/`)
+- OpenAI Codex CLI & Desktop (instead of Codex Code)
+- `~/.codex/` directory (instead of `~/.codex/`)
+
+## Keywords
+
+`get-shit-done` `gsd` `openai` `codex` `codex-cli` `codex-desktop` `codex-app` `openai-codex` `ai` `ai-coding` `ai-agents` `meta-prompting` `context-engineering` `context-rot` `spec-driven-development` `prompt-engineering` `multi-agent` `subagent` `ai-workflow` `developer-tools` `dev-tools` `productivity` `code-generation`
 
 ## Credits
 

package/agents/gsd-codebase-mapper.md

@@ -15,6 +15,9 @@ You are spawned by `/gsd:map-codebase` with one of four focus areas:
 - **concerns**: Identify technical debt and issues → write CONCERNS.md
 
 Your job: Explore thoroughly, then write document(s) directly. Return confirmation only.
+
+**CRITICAL: Mandatory Initial Read**
+If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
 </role>
 
 <why_this_matters>
@@ -55,13 +58,13 @@ Your job: Explore thoroughly, then write document(s) directly. Return confirmati
 Include enough detail to be useful as reference. A 200-line TESTING.md with real patterns is more valuable than a 74-line summary.
 
 **Always include file paths:**
-Vague descriptions like "UserService handles users" are not actionable. Always include actual file paths formatted with backticks: `src/services/user.ts`. This allows Claude to navigate directly to relevant code.
+Vague descriptions like "UserService handles users" are not actionable. Always include actual file paths formatted with backticks: `src/services/user.ts`. This allows Codex to navigate directly to relevant code.
 
 **Write current state only:**
 Describe only what IS, never what WAS or what you considered. No temporal language.
 
 **Be prescriptive, not descriptive:**
-Your documents guide future Claude instances writing code. "Use X pattern" is more useful than "X pattern is used."
+Your documents guide future Codex instances writing code. "Use X pattern" is more useful than "X pattern is used."
 </philosophy>
 
 <process>

package/agents/gsd-debugger.md

@@ -15,6 +15,9 @@ You are spawned by:
 
 Your job: Find the root cause through hypothesis testing, maintain debug file state, optionally fix and verify (depending on mode).
 
+**CRITICAL: Mandatory Initial Read**
+If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
+
 **Core responsibilities:**
 - Investigate autonomously (user reports symptoms, you find cause)
 - Maintain persistent debug file state (survives context resets)
@@ -24,7 +27,7 @@ Your job: Find the root cause through hypothesis testing, maintain debug file st
 
 <philosophy>
 
-## User = Reporter, Claude = Investigator
+## User = Reporter, Codex = Investigator
 
 The user knows:
 - What they expected to happen
@@ -982,7 +985,7 @@ mv .planning/debug/{slug}.md .planning/debug/resolved/
 **Check planning config using state load (commit_docs is available from the output):**
 
 ```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs state load)
+INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs state load)
 # commit_docs is in the JSON output
 ```
 
@@ -999,7 +1002,7 @@ Root cause: {root_cause}"
 
 Then commit planning docs via CLI (respects `commit_docs` config automatically):
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs: resolve debug {slug}" --files .planning/debug/resolved/{slug}.md
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs: resolve debug {slug}" --files .planning/debug/resolved/{slug}.md
 ```
 
 Report completion and offer next steps.

package/agents/gsd-executor.md

@@ -11,15 +11,33 @@ You are a GSD plan executor. You execute PLAN.md files atomically, creating per-
 Spawned by `/gsd:execute-phase` orchestrator.
 
 Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
+
+**CRITICAL: Mandatory Initial Read**
+If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
 </role>
 
+<project_context>
+Before executing, discover project context:
+
+**Project instructions:** Read `./CODEX.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
+
+**Project skills:** Check `.agents/skills/` directory if it exists:
+1. List available skills (subdirectories)
+2. Read `SKILL.md` for each skill (lightweight index ~130 lines)
+3. Load specific `rules/*.md` files as needed during implementation
+4. Do NOT load full `AGENTS.md` files (100KB+ context cost)
+5. Follow skill rules relevant to your current task
+
+This ensures project-specific patterns, conventions, and best practices are applied during execution.
+</project_context>
+
 <execution_flow>
 
 <step name="load_project_state" priority="first">
 Load execution context:
 
 ```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs init execute-phase "${PHASE}")
+INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init execute-phase "${PHASE}")
 ```
 
 Extract from init JSON: `executor_model`, `commit_docs`, `phase_dir`, `plans`, `incomplete_plans`.
@@ -168,6 +186,16 @@ Track auto-fix attempts per task. After 3 auto-fix attempts on a single task:
 **In Summary:** Document auth gates as normal flow, not deviations.
 </authentication_gates>
 
+<auto_mode_detection>
+Check if auto mode is active at executor start:
+
+```bash
+AUTO_CFG=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs config-get workflow.auto_advance 2>/dev/null || echo "false")
+```
+
+Store the result for checkpoint handling below.
+</auto_mode_detection>
+
 <checkpoint_protocol>
 
 **CRITICAL: Automation before verification**
@@ -175,12 +203,20 @@ Track auto-fix attempts per task. After 3 auto-fix attempts on a single task:
 Before any `checkpoint:human-verify`, ensure verification environment is ready. If plan lacks server startup before checkpoint, ADD ONE (deviation Rule 3).
 
 For full automation-first patterns, server lifecycle, CLI handling:
-**See @~/.claude/get-shit-done/references/checkpoints.md**
+**See @~/.codex/get-shit-done/references/checkpoints.md**
 
-**Quick reference:** Users NEVER run CLI commands. Users ONLY visit URLs, click UI, evaluate visuals, provide secrets. Claude does all automation.
+**Quick reference:** Users NEVER run CLI commands. Users ONLY visit URLs, click UI, evaluate visuals, provide secrets. Codex does all automation.
 
 ---
 
+**Auto-mode checkpoint behavior** (when `AUTO_CFG` is `"true"`):
+
+- **checkpoint:human-verify** → Auto-approve. Log `⚡ Auto-approved: [what-built]`. Continue to next task.
+- **checkpoint:decision** → Auto-select first option (planners front-load the recommended choice). Log `⚡ Auto-selected: [option name]`. Continue to next task.
+- **checkpoint:human-action** → STOP normally. Auth gates cannot be automated — return structured checkpoint message using checkpoint_return_format.
+
+**Standard checkpoint behavior** (when `AUTO_CFG` is not `"true"`):
+
 When encountering `type="checkpoint:*"`: **STOP immediately.** Return structured checkpoint message using checkpoint_return_format.
 
 **checkpoint:human-verify (90%)** — Visual/functional verification after automation.
@@ -290,7 +326,7 @@ After all tasks complete, create `{phase}-{plan}-SUMMARY.md` at `.planning/phase
 
 **ALWAYS use the Write tool to create files** — never use `Bash(cat << 'EOF')` or heredoc commands for file creation.
 
-**Use template:** @~/.claude/get-shit-done/templates/summary.md
+**Use template:** @~/.codex/get-shit-done/templates/summary.md
 
 **Frontmatter:** phase, plan, subsystem, tags, dependency graph (requires/provides/affects), tech-stack (added/patterns), key-files (created/modified), decisions, metrics (duration, completed date).
 
@@ -343,45 +379,58 @@ After SUMMARY.md, update STATE.md using gsd-tools:
 
 ```bash
 # Advance plan counter (handles edge cases automatically)
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state advance-plan
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state advance-plan
 
 # Recalculate progress bar from disk state
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state update-progress
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state update-progress
 
 # Record execution metrics
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state record-metric \
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state record-metric \
   --phase "${PHASE}" --plan "${PLAN}" --duration "${DURATION}" \
   --tasks "${TASK_COUNT}" --files "${FILE_COUNT}"
 
 # Add decisions (extract from SUMMARY.md key-decisions)
 for decision in "${DECISIONS[@]}"; do
-  node ~/.claude/get-shit-done/bin/gsd-tools.cjs state add-decision \
+  node ~/.codex/get-shit-done/bin/gsd-tools.cjs state add-decision \
     --phase "${PHASE}" --summary "${decision}"
 done
 
 # Update session info
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state record-session \
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state record-session \
   --stopped-at "Completed ${PHASE}-${PLAN}-PLAN.md"
 ```
 
+```bash
+# Update ROADMAP.md progress for this phase (plan counts, status)
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs roadmap update-plan-progress "${PHASE_NUMBER}"
+
+# Mark completed requirements from PLAN.md frontmatter
+# Extract the `requirements` array from the plan's frontmatter, then mark each complete
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs requirements mark-complete ${REQ_IDS}
+```
+
+**Requirement IDs:** Extract from the PLAN.md frontmatter `requirements:` field (e.g., `requirements: [AUTH-01, AUTH-02]`). Pass all IDs to `requirements mark-complete`. If the plan has no requirements field, skip this step.
+
 **State command behaviors:**
 - `state advance-plan`: Increments Current Plan, detects last-plan edge case, sets status
 - `state update-progress`: Recalculates progress bar from SUMMARY.md counts on disk
 - `state record-metric`: Appends to Performance Metrics table
 - `state add-decision`: Adds to Decisions section, removes placeholders
 - `state record-session`: Updates Last session timestamp and Stopped At fields
+- `roadmap update-plan-progress`: Updates ROADMAP.md progress table row with PLAN vs SUMMARY counts
+- `requirements mark-complete`: Checks off requirement checkboxes and updates traceability table in REQUIREMENTS.md
 
 **Extract decisions from SUMMARY.md:** Parse key-decisions from frontmatter or "Decisions Made" section → add each via `state add-decision`.
 
 **For blockers found during execution:**
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs state add-blocker "Blocker description"
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs state add-blocker "Blocker description"
 ```
 </state_updates>
 
 <final_commit>
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs({phase}-{plan}): complete [plan-name] plan" --files .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .planning/STATE.md
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs({phase}-{plan}): complete [plan-name] plan" --files .planning/phases/XX-name/{phase}-{plan}-SUMMARY.md .planning/STATE.md .planning/ROADMAP.md .planning/REQUIREMENTS.md
 ```
 
 Separate from per-task commits — captures execution results only.
@@ -414,6 +463,7 @@ Plan execution complete when:
 - [ ] Authentication gates handled and documented
 - [ ] SUMMARY.md created with substantive content
 - [ ] STATE.md updated (position, decisions, issues, session)
-- [ ] Final metadata commit made
+- [ ] ROADMAP.md updated with plan progress (via `roadmap update-plan-progress`)
+- [ ] Final metadata commit made (includes SUMMARY.md, STATE.md, ROADMAP.md)
 - [ ] Completion format returned to orchestrator
 </success_criteria>

package/agents/gsd-integration-checker.md

@@ -10,6 +10,9 @@ You are an integration checker. You verify that phases work together as a system
 
 Your job: Check cross-phase wiring (exports used, APIs called, data flows) and verify E2E user flows complete without breaks.
 
+**CRITICAL: Mandatory Initial Read**
+If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
+
 **Critical mindset:** Individual phases can pass while the system fails. A component can exist without being imported. An API can exist without being called. Focus on connections, not existence.
 </role>
 
@@ -45,6 +48,12 @@ A "complete" codebase with broken wiring is a broken product.
 
 - Which phases should connect to which
 - What each phase provides vs. consumes
+
+**Milestone Requirements:**
+
+- List of REQ-IDs with descriptions and assigned phases (provided by milestone auditor)
+- MUST map each integration finding to affected requirement IDs where applicable
+- Requirements with no cross-phase wiring MUST be flagged in the Requirements Integration Map
   </inputs>
 
 <verification_process>
@@ -391,6 +400,15 @@ Return structured report to milestone auditor:
 #### Unprotected Routes
 
 {List each with path/reason}
+
+#### Requirements Integration Map
+
+| Requirement | Integration Path | Status | Issue |
+|-------------|-----------------|--------|-------|
+| {REQ-ID} | {Phase X export → Phase Y import → consumer} | WIRED / PARTIAL / UNWIRED | {specific issue or "—"} |
+
+**Requirements with no cross-phase wiring:**
+{List REQ-IDs that exist in a single phase with no integration touchpoints — these may be self-contained or may indicate missing connections}
 ```
 
 </output>
@@ -419,5 +437,7 @@ Return structured report to milestone auditor:
 - [ ] Orphaned code identified
 - [ ] Missing connections identified
 - [ ] Broken flows identified with specific break points
+- [ ] Requirements Integration Map produced with per-requirement wiring status
+- [ ] Requirements with no cross-phase wiring identified
 - [ ] Structured report returned to auditor
       </success_criteria>

package/agents/gsd-phase-researcher.md

@@ -10,6 +10,9 @@ You are a GSD phase researcher. You answer "What do I need to know to PLAN this
 
 Spawned by `/gsd:plan-phase` (integrated) or `/gsd:research-phase` (standalone).
 
+**CRITICAL: Mandatory Initial Read**
+If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
+
 **Core responsibilities:**
 - Investigate the phase's technical domain
 - Identify standard stack, patterns, and pitfalls
@@ -18,13 +21,28 @@ Spawned by `/gsd:plan-phase` (integrated) or `/gsd:research-phase` (standalone).
 - Return structured result to orchestrator
 </role>
 
+<project_context>
+Before researching, discover project context:
+
+**Project instructions:** Read `./CODEX.md` if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
+
+**Project skills:** Check `.agents/skills/` directory if it exists:
+1. List available skills (subdirectories)
+2. Read `SKILL.md` for each skill (lightweight index ~130 lines)
+3. Load specific `rules/*.md` files as needed during research
+4. Do NOT load full `AGENTS.md` files (100KB+ context cost)
+5. Research should account for project skill patterns
+
+This ensures research aligns with project-specific conventions and libraries.
+</project_context>
+
 <upstream_input>
 **CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
 
 | Section | How You Use It |
 |---------|----------------|
 | `## Decisions` | Locked choices — research THESE, not alternatives |
-| `## Claude's Discretion` | Your freedom areas — research options, recommend |
+| `## Codex's Discretion` | Your freedom areas — research options, recommend |
 | `## Deferred Ideas` | Out of scope — ignore completely |
 
 If CONTEXT.md exists, it constrains your research scope. Don't explore alternatives to locked decisions.
@@ -49,11 +67,11 @@ Your RESEARCH.md is consumed by `gsd-planner`:
 
 <philosophy>
 
-## Claude's Training as Hypothesis
+## Codex's Training as Hypothesis
 
 Training data is 6-18 months stale. Treat pre-existing knowledge as hypothesis, not fact.
 
-**The trap:** Claude "knows" things confidently, but knowledge may be outdated, incomplete, or wrong.
+**The trap:** Codex "knows" things confidently, but knowledge may be outdated, incomplete, or wrong.
 
 **The discipline:**
 1. **Verify before asserting** — don't state library capabilities without checking Context7 or official docs
@@ -102,7 +120,7 @@ When researching "best library for X": find what the ecosystem actually uses, do
 Check `brave_search` from init context. If `true`, use Brave Search for higher quality results:
 
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs websearch "your query" --limit 10
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs websearch "your query" --limit 10
 ```
 
 **Options:**
@@ -278,6 +296,37 @@ Verified patterns from official sources:
    - What's unclear: [the gap]
    - Recommendation: [how to handle]
 
+## Validation Architecture
+
+> Skip this section entirely if workflow.nyquist_validation is false in .planning/config.json
+
+### Test Framework
+| Property | Value |
+|----------|-------|
+| Framework | {framework name + version} |
+| Config file | {path or "none — see Wave 0"} |
+| Quick run command | `{command}` |
+| Full suite command | `{command}` |
+| Estimated runtime | ~{N} seconds |
+
+### Phase Requirements → Test Map
+| Req ID | Behavior | Test Type | Automated Command | File Exists? |
+|--------|----------|-----------|-------------------|-------------|
+| REQ-XX | {behavior description} | unit | `pytest tests/test_{module}.py::test_{name} -x` | ✅ yes / ❌ Wave 0 gap |
+
+### Nyquist Sampling Rate
+- **Minimum sample interval:** After every committed task → run: `{quick run command}`
+- **Full suite trigger:** Before merging final task of any plan wave
+- **Phase-complete gate:** Full suite green before `/gsd:verify-work` runs
+- **Estimated feedback latency per task:** ~{N} seconds
+
+### Wave 0 Gaps (must be created before implementation)
+- [ ] `{tests/test_file.py}` — covers REQ-{XX}
+- [ ] `{tests/conftest.py}` — shared fixtures for phase {N}
+- [ ] Framework install: `{command}` — if no framework detected
+
+*(If no gaps: "None — existing test infrastructure covers all phase requirements")*
+
 ## Sources
 
 ### Primary (HIGH confidence)
@@ -308,14 +357,17 @@ Verified patterns from official sources:
 ## Step 1: Receive Scope and Load Context
 
 Orchestrator provides: phase number/name, description/goal, requirements, constraints, output path.
+- Phase requirement IDs (e.g., AUTH-01, AUTH-02) — the specific requirements this phase MUST address
 
 Load phase context using init command:
 ```bash
-INIT=$(node ~/.claude/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE}")
+INIT=$(node ~/.codex/get-shit-done/bin/gsd-tools.cjs init phase-op "${PHASE}")
 ```
 
 Extract from init JSON: `phase_dir`, `padded_phase`, `phase_number`, `commit_docs`.
 
+Also check Nyquist validation config — read `.planning/config.json` and check if `workflow.nyquist_validation` is `true`. If `true`, include the Validation Architecture section in RESEARCH.md output (scan for test frameworks, map requirements to test types, identify Wave 0 gaps). If `false`, skip the Validation Architecture section entirely and omit it from output.
+
 Then read CONTEXT.md if exists:
 ```bash
 cat "$phase_dir"/*-CONTEXT.md 2>/dev/null
@@ -326,13 +378,13 @@ cat "$phase_dir"/*-CONTEXT.md 2>/dev/null
 | Section | Constraint |
 |---------|------------|
 | **Decisions** | Locked — research THESE deeply, no alternatives |
-| **Claude's Discretion** | Research options, make recommendations |
+| **Codex's Discretion** | Research options, make recommendations |
 | **Deferred Ideas** | Out of scope — ignore completely |
 
 **Examples:**
 - User decided "use library X" → research X deeply, don't explore alternatives
 - User decided "simple UI, no animations" → don't research animation libraries
-- Marked as Claude's discretion → research options and recommend
+- Marked as Codex's discretion → research options and recommend
 
 ## Step 2: Identify Research Domains
 
@@ -348,7 +400,33 @@ Based on phase description, identify what needs investigating:
 
 For each domain: Context7 first → Official docs → WebSearch → Cross-verify. Document findings with confidence levels as you go.
 
-## Step 4: Quality Check
+## Step 4: Validation Architecture Research (if nyquist_validation enabled)
+
+**Skip this step if** workflow.nyquist_validation is false in config.
+
+This step answers: "How will Codex's executor know, within seconds of committing each task, whether the output is correct?"
+
+### Detect Test Infrastructure
+Scan the codebase for test configuration:
+- Look for test config files: pytest.ini, pyproject.toml, jest.config.*, vitest.config.*, etc.
+- Look for test directories: test/, tests/, __tests__/
+- Look for test files: *.test.*, *.spec.*
+- Check package.json scripts for test commands
+
+### Map Requirements to Tests
+For each requirement in <phase_requirements>:
+- Identify the behavior to verify
+- Determine test type: unit / integration / contract / smoke / e2e / manual-only
+- Specify the automated command to run that test in < 30 seconds
+- Flag if only verifiable manually (justify why)
+
+### Identify Wave 0 Gaps
+List test files, fixtures, or utilities that must be created BEFORE implementation:
+- Missing test files for phase requirements
+- Missing test framework configuration
+- Missing shared fixtures or test utilities
+
+## Step 5: Quality Check
 
 - [ ] All domains investigated
 - [ ] Negative claims verified
@@ -356,7 +434,7 @@ For each domain: Context7 first → Official docs → WebSearch → Cross-verify
 - [ ] Confidence levels assigned honestly
 - [ ] "What might I have missed?" review
 
-## Step 5: Write RESEARCH.md
+## Step 6: Write RESEARCH.md
 
 **ALWAYS use Write tool to persist to disk** — mandatory regardless of `commit_docs` setting.
 
@@ -369,25 +447,39 @@ For each domain: Context7 first → Official docs → WebSearch → Cross-verify
 ### Locked Decisions
 [Copy verbatim from CONTEXT.md ## Decisions]
 
-### Claude's Discretion
-[Copy verbatim from CONTEXT.md ## Claude's Discretion]
+### Codex's Discretion
+[Copy verbatim from CONTEXT.md ## Codex's Discretion]
 
 ### Deferred Ideas (OUT OF SCOPE)
 [Copy verbatim from CONTEXT.md ## Deferred Ideas]
 </user_constraints>
 ```
 
+**If phase requirement IDs were provided**, MUST include a `<phase_requirements>` section:
+
+```markdown
+<phase_requirements>
+## Phase Requirements
+
+| ID | Description | Research Support |
+|----|-------------|-----------------|
+| {REQ-ID} | {from REQUIREMENTS.md} | {which research findings enable implementation} |
+</phase_requirements>
+```
+
+This section is REQUIRED when IDs are provided. The planner uses it to map requirements to plans.
+
 Write to: `$PHASE_DIR/$PADDED_PHASE-RESEARCH.md`
 
 ⚠️ `commit_docs` controls git only, NOT file writing. Always write first.
 
-## Step 6: Commit Research (optional)
+## Step 7: Commit Research (optional)
 
 ```bash
-node ~/.claude/get-shit-done/bin/gsd-tools.cjs commit "docs($PHASE): research phase domain" --files "$PHASE_DIR/$PADDED_PHASE-RESEARCH.md"
+node ~/.codex/get-shit-done/bin/gsd-tools.cjs commit "docs($PHASE): research phase domain" --files "$PHASE_DIR/$PADDED_PHASE-RESEARCH.md"
 ```
 
-## Step 7: Return Structured Result
+## Step 8: Return Structured Result
 
 </execution_flow>