Follow an AI task and review its changes

Write a focused request, answer questions, and review the changes before they reach your project.

On this page

When you hand a task to AI, PlayWeld shows the request, questions, approvals, and changed files as work progresses. A focused request makes it easier to follow the work and judge the result.

Prepare a request

Open a registered, trusted project. Configure a model that supports the required tool workflow and make sure relevant roles and skills are eligible. Where Git worktrees are required, start from an appropriate clean workspace.

Name the result precisely. For example, ask for a documented countdown rule in docs/DESIGN.md, including when it starts and resets. Keep a documentation task distinct from an instruction to implement gameplay.

Submit and follow the task

  1. Select the project, coordinator role, and token budget.
  2. Use Preview impact with concrete file paths or canon IDs.
  3. Read the preview, then submit the request when its scope is appropriate.
  4. Inspect the task tree and answer questions attached to the correct task.
  5. Review individual tool approvals and retain any failure diagnostics.

A task waiting for an answer about the example workflow

This real task-runtime exercise uses a scripted provider and a disposable project.

An impact preview does not execute the task. An empty dependency result does not prove that a change has no consequences.

Inspect the integration boundary

Read the changed files, test evidence, and reported conflicts. A child task can finish successfully while its changes remain in a separate worktree. Inspect its integration row, apply a ready change through the offered control when appropriate, and verify the workspace diff afterward.

Completed work with a separate ready integration

The generated example document tests the integration workflow; it is not a demonstrated gameplay implementation.

When conflicts occur, keep the worktree and diagnostics while resolving the actual conflict. Cancelling a task does not undo an external operation that already completed. Before accepting gameplay changes, run the relevant engine checks and compare the result with the design. Reconcile Knowledge after adopted document changes.

More detail

Configure AI workflows ยท Step 5 of 5

Did this guide help?

Report a missing or incorrect detail
Mention your PlayWeld or engine version if it matters. Leave out private project details.

100%

Use left and right arrow keys to browse. Press Escape to close.