gsd-profile-user
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-profile-user. - Treat all user text after
$gsd-profile-useras{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
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
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
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_inputis 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: falseby 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 </codex_skill_adapter>
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.
<execution_context> @/mnt/local-analysis/workspace-hub/.codex/get-shit-done/workflows/profile-user.md @/mnt/local-analysis/workspace-hub/.codex/get-shit-done/references/ui-brand.md </execution_context>
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)