Studio Assistant Workflow Guide

Workflow Design Heuristics

• Prefer small, legible role splits over a large generic team.
• Give each performer a distinct responsibility and a clear handoff.
• If the workflow naturally has stages, mirror those stages in relation order.
• If the user asks for review, approval, or escalation, model those as explicit relations rather than vague shared responsibility.
• If a workflow can plausibly be solved with one performer, say so instead of forcing an Act.

Common Patterns

Single Expert

• One performer with a clear role name
• Add model, Tal, Dances, and MCP only when explicitly known

Research -> Writer

• Researcher gathers and structures findings
• Writer turns findings into polished output
• Relation should include a concrete name and description

Code Review Loop

• Developer writes code
• Reviewer reviews and returns feedback
• If both directions are needed, create two separate one-way relations

Small Delivery Team

• Planner or PM
• Builder
• Reviewer or QA
• Keep relations minimal and explicit

Response Strategy

• State the intended structure briefly.
• If the request is underspecified, ask the smallest clarifying question needed.
• If the request already names the target roles and workflow shape, skip the extra confirmation step and create the concrete structure directly.
• Asset creation can be conversational. Use a short question-and-answer flow when the correct Performer or Act shape depends on missing intent.
• When Tal, Dance, or Performer setup can be done in more than one reasonable way, present the shortest useful option set first.
• If the request is specific enough, create the concrete performer and Act structure directly.
• Before finalizing a non-trivial mutation payload, make sure same-call refs, draft kinds, and workflow relations are all valid before calling apply_studio_actions.

Anti-Patterns

• Creating several generic performers with overlapping jobs.
• Returning an unconnected multi-participant Act for a workflow request.
• Ignoring a role the user explicitly asked for because a simpler topology exists.
• Adding Tal, Dance, or model choices that the user explicitly asked to omit.