Planning and Package Builds

Export

Use a plan when a request has several responsibilities, depends on your own APIs, or needs more than one file. A plan lets you review the design before asking Atlas to implement it.

Create and refine a plan

/plan Build a reusable door interaction for my guard AI. Prefer built-in movement tasks. Use my DoorController API for opening and closing. List the files, inspector references, and interruption tests before generating code.

An illustrative door-interaction plan with the Save plan action.

Attach the existing controller and relevant graph. Check the plan for:

  • Responsibilities that can use built-in objects.
  • Existing project APIs that should be reused.
  • Which component owns movement, animation, input, and temporary state.
  • Files to create or modify, and their intended destinations.
  • Required inspector assignments and a concrete test for each behavior.

Revise the plan in the same chat. For example, “The controller already owns animation; remove animation handling from the tasks.” Choose Save plan… to keep a Markdown copy inside the project.

Build the plan

When the plan is ready, say:

Build the plan.

Atlas uses the latest plan in the conversation to create a dependency-ordered set of C# files and generates it in batches. A larger plan is not limited to the ordinary selected-file modification count. Keep the scope manageable so you can review and test the complete feature.

An illustrative complete multi-file result ready for destination selection and review.

Incomplete package batches stay staged until the complete manifest is ready. When it finishes, inspect every file and choose an Assets/... package destination. Apply all preserves the planned responsibility folders. Configuration of your scene, graph, or character remains a separate step unless the result explicitly provides a supported workflow for it.

Resume interrupted work

An interrupted example package with a Resume package build action.

If Resume package build appears, wait until Unity is ready and use it to continue the existing package. Avoid creating a second chat with the same build request while the first result is still recoverable.

After a completed apply, let Unity compile and test the dependency chain from the smallest component upward. If writing a batch fails, Atlas attempts to restore earlier file contents; inspect the project and error before retrying. Source control remains the reliable way to review and restore your project.

See Generating and applying code for destinations and access settings, and Project instructions for folder-specific conventions.