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-user as {{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 → header
• question → 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 </codex_skill_adapter>

<objective> Generate 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.

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. </objective>

<execution_context> @/Users/gabrielwillen/VSCode/stateforward/emel/emel.cpp/.codex/get-shit-done/workflows/profile-user.md @/Users/gabrielwillen/VSCode/stateforward/emel/emel.cpp/.codex/get-shit-done/references/ui-brand.md </execution_context>

<context> Flags from {{GSD_ARGS}}: - `--questionnaire` -- Skip session analysis entirely, use questionnaire-only path - `--refresh` -- Rebuild profile even when one exists, backup old profile, show dimension diff </context> <process> Execute the profile-user workflow end-to-end.

The workflow handles all logic including:

1. Initialization and existing profile detection
2. Consent gate before session analysis
3. Session scanning and data sufficiency checks
4. Session analysis (profiler agent) or questionnaire fallback
5. Cross-project split resolution
6. Profile writing to USER-PROFILE.md
7. Result display with report card and highlights
8. Artifact selection (dev-preferences, AGENTS.md sections)
9. Sequential artifact generation
10. Summary with refresh diff (if applicable) </process>