Gsd Profile User

D. Subagent Spawning

When the workflow needs to spawn a subagent:

• Use Task(subagent_type="generalPurpose", ...)
• The model parameter maps to Cursor's model options (e.g., "fast") </cursor_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. </objective>

<execution_context> @/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/workflows/profile-user.md @/Users/zaneliu/Projects/open-source/cloud-cli-proxy/.cursor/get-shit-done/references/ui-brand.md </execution_context>

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, .cursor/rules/ sections)
9. Sequential artifact generation
10. Summary with refresh diff (if applicable)