Who should use the Roleplaying workflow?
Teams or solo builders working on work tasks who want a repeatable process instead of one-off tool experiments.
Execution Map
4-step pipeline — follow each step in order
1Setup · Step 1 of 4
Open task pageAI Girlfriend
Prepare inputs and settings through AI Girlfriend before running roleplaying.
Why this matters
AI Girlfriend sets up the foundation for roleplaying; clean inputs here reduce downstream rework.
What you get
Inputs, context, and settings are ready so the workflow can move into execution without blockers.
2Core · Step 2 of 4
Open task pageRoleplaying
Execute roleplaying with Roleplaying to produce the primary final deliverable.
Why this matters
This is the core step where roleplaying actually happens, so it determines baseline quality for everything after it.
What you get
A first-pass final deliverable is generated and ready for refinement in the next steps.
More options
3Refine · Step 3 of 4
Open task pageAI Boyfriend
Refine and validate roleplaying output using AI Boyfriend before final delivery.
Why this matters
AI Boyfriend adds quality control so issues are caught before the workflow is finalized.
What you get
The final deliverable is improved, validated, and prepared for final delivery.
4Deliver · Step 4 of 4
Open task pageVirtual Friend
Package and ship the output through Virtual Friend so roleplaying reaches end users.
Why this matters
Virtual Friend is what turns intermediate output into a usable, publishable result for real users.
What you get
A finalized final deliverable is ready for publishing, handoff, or integration.