Plan and Forge
Plan and Forge make the boundary between reasoning and action explicit across the EngineForge Crew.
Plan and Forge in the Cockpit
Follow the Project Starfall interaction in the selected demo appearance.
Plan
Plan is read-only. Maestro can inspect project context, reason about the objective, identify risks, and prepare bounded specialist tasks without changing files or engine state.
Forge
Forge enables implementation through the allowed tools of a specialist called by Maestro. The exact actions depend on the role, project, engine connection, and approval policy.
Recommended flow
- State a bounded objective.
- Use Plan to inspect context and agree on a direction.
- Let Maestro identify the specialist useful for the next step.
- Move to Forge and handle any approval request.
- Review changed files, diffs, and runtime evidence.
Expected state
The composer shows the active mode and Crew configuration. Plan must not write. Forge activity remains visible through agent output, approvals, session changes, and evidence.
Limitations
Forge is not permission for unrestricted action. Success still requires review, and engine actions require the corresponding bridge/runtime state.