Crew
Crew is EngineForge’s extensible system of game-development specialists. Maestro coordinates the current roster; the five roles are a starting point, not the limit of the system.
Build a Crew for the session
In Project Starfall, remove Playtester from this session and choose Juicer as the lead.
Starting roster
These roles establish the current Crew coordination model while leaving room for additional specialists and capabilities.
- Maestro: Coordinates specialist work, checks its verification, and decides when independent testing is useful.
- Prototyper: Builds the first playable slice.
- Juicer: Improves feel, feedback, and presentation.
- Systems Smith: Builds durable systems, UI, and persistence.
- Playtester: Runs the game and verifies behavior from evidence.
Choose by objective
Maestro coordinates the task. Prototyper builds a first playable slice, Juicer improves feel and presentation, Systems Smith builds durable systems and UI, and Playtester investigates runtime behavior from evidence.
Serial specialist tools
Maestro uses serial specialist tool calls when a specialist’s role is useful to the task. Not every request delegates or re-verifies: straightforward work can remain with the relevant specialist and the available evidence.
Verification and checks
Verification is specialist-owned: the specialist reports what it checked and the evidence it observed. Maestro records sanity checks against that report and uses conditional independent testing only when the task warrants a separate check.
Plan and Forge behavior
Every role can inspect and coordinate in read-only Plan. Forge exposes only the tools appropriate to the selected role rather than giving every specialist the same action surface.
Growth model and scope
The Crew architecture can expand with additional specialists and capabilities. Specialist workflow redesign is a later phase; current documentation covers the active roles without announcing future role names, dates, or a universal workflow.
Limitations
The Crew does not remove developer responsibility. Availability can depend on the active project, mode, engine state, and required approvals.