Survival Rpg Orchestrator

Apply these default routing rules.

• New gameplay feature: use $survival-rpg-project, then add $unreal-lyra-expert if the feature touches runtime implementation.
• Combat, progression, gathering, crafting, portals, bosses, runes, or world events: use both skills unless the user is only discussing design direction.
• Refactor, bug fix, review, replication, GAS ability work, or subsystem placement: use $unreal-lyra-expert and keep $survival-rpg-project active if the change could shift the game's identity or scope.
• Documentation, prioritization, feature triage, or MVP planning: use $survival-rpg-project first and only add $unreal-lyra-expert when technical constraints matter.

Turn large requests into a stable execution sequence.

• Step 1: restate the concrete deliverable internally.
• Step 2: load the relevant project and technical skills.
• Step 3: inspect the local repository before proposing structure changes.
• Step 4: choose the smallest slice that proves fun, clarity, or architectural soundness.
• Step 5: implement or document that slice.
• Step 6: verify the result and call out remaining risks.

Use sub-agents only when the task is explicitly large enough to benefit from delegation.

• Prefer local execution for small or tightly coupled work.
• Split only into concrete, non-overlapping subtasks with clear ownership.
• Good delegation examples: one agent explores affected gameplay files, another implements a UI slice, another reviews replication risks.
• Avoid delegation when the next action is blocked on a small local answer.
• When delegating, keep the project skill active in the framing so all agents stay aligned with the same product guardrails.

Use these orchestration priorities when tradeoffs appear.

• Product identity outranks convenience.
• First playable outranks feature breadth.
• Clear architecture outranks speculative abstraction.
• Data-driven extension points outrank hard-coded content.
• Fun and readability outrank simulation depth.

Catch coordination failures early.

• Stop scope drift toward MMO structure, pure sandbox building, or punitive survival micromanagement.
• Stop technical drift toward hard-coded content, oversized managers, or systems that bypass Unreal and Lyra extension seams already present.
• Stop planning drift when a task grows beyond the current vertical-slice goal.

When reporting back, summarize in this order.

• Which specialist skills were activated and why.
• What concrete slice was chosen.
• What was implemented, reviewed, or deferred.
• What risks or next steps remain.

State assumptions explicitly when context is incomplete.

• Name the files, systems, or design goals used to classify the task.
• If there is no project documentation yet, use $survival-rpg-project as the temporary source of truth and recommend creating docs when the same decisions repeat.