B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header → headerquestion → question- Options formatted as
"Label" — description → {label: "Label", description: "description"}
- Generate
id from header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2]) → single request_user_input with multiple entries in questions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_input is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y") → spawn_agent(agent_type="X", message="Y")Task(model="...") → omit (Codex uses per-role config, not inline model selection)fork_context: false by default — GSD agents load their own context via <files_to_read> blocks
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids) for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT, PLAN COMPLETE, SUMMARY, etc.
close_agent(id) after collecting results from each agent
Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.
The workflow handles all logic including:
- Initialization and existing profile detection
- Consent gate before session analysis
- Session scanning and data sufficiency checks
- Session analysis (profiler agent) or questionnaire fallback
- Cross-project split resolution
- Profile writing to USER-PROFILE.md
- Result display with report card and highlights
- Artifact selection (dev-preferences, AGENTS.md sections)
- Sequential artifact generation
- Summary with refresh diff (if applicable)
1---2name: "gsd-profile-user"3description: "Generate developer behavioral profile and create Claude-discoverable artifacts"4metadata:5 short-description: "Generate developer behavioral profile and create Claude-discoverable artifacts"6---78<codex_skill_adapter>9## A. Skill Invocation10- This skill is invoked by mentioning `$gsd-profile-user`.11- Treat all user text after `$gsd-profile-user` as `{{GSD_ARGS}}`.12- If no arguments are present, treat `{{GSD_ARGS}}` as empty.1314## B. AskUserQuestion → request_user_input Mapping15GSD workflows use `AskUserQuestion` (Claude Code syntax). Translate to Codex `request_user_input`:1617Parameter mapping:18- `header` → `header`19- `question` → `question`20- Options formatted as `"Label" — description` → `{label: "Label", description: "description"}`21- Generate `id` from header: lowercase, replace spaces with underscores2223Batched calls:24- `AskUserQuestion([q1, q2])` → single `request_user_input` with multiple entries in `questions[]`2526Multi-select workaround:27- Codex has no `multiSelect`. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.2829Execute mode fallback:30- When `request_user_input` is rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.3132## C. Task() → spawn_agent Mapping33GSD workflows use `Task(...)` (Claude Code syntax). Translate to Codex collaboration tools:3435Direct mapping:36- `Task(subagent_type="X", prompt="Y")` → `spawn_agent(agent_type="X", message="Y")`37- `Task(model="...")` → omit (Codex uses per-role config, not inline model selection)38- `fork_context: false` by default — GSD agents load their own context via `<files_to_read>` blocks3940Parallel fan-out:41- Spawn multiple agents → collect agent IDs → `wait(ids)` for all to complete4243Result parsing:44- Look for structured markers in agent output: `CHECKPOINT`, `PLAN COMPLETE`, `SUMMARY`, etc.45- `close_agent(id)` after collecting results from each agent46</codex_skill_adapter>4748<objective>49Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, $gsd-dev-preferences, AGENTS.md section) that personalize the agent's responses.5051Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.52</objective>5354<execution_context>55@/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/workflows/profile-user.md56@/Users/richardhightower/clients/spillwave/src/agent-brain/.codex/get-shit-done/references/ui-brand.md57</execution_context>5859<context>60Flags from {{GSD_ARGS}}:61- `--questionnaire` -- Skip session analysis entirely, use questionnaire-only path62- `--refresh` -- Rebuild profile even when one exists, backup old profile, show dimension diff63</context>6465<process>66Execute the profile-user workflow end-to-end.6768The workflow handles all logic including:691. Initialization and existing profile detection702. Consent gate before session analysis713. Session scanning and data sufficiency checks724. Session analysis (profiler agent) or questionnaire fallback735. Cross-project split resolution746. Profile writing to USER-PROFILE.md757. Result display with report card and highlights768. Artifact selection (dev-preferences, AGENTS.md sections)779. Sequential artifact generation7810. Summary with refresh diff (if applicable)79</process>
SpillwaveSolutions