#Plans

A plan is an ordered list of steps the builder agent intends to follow when executing a work item. No execution begins until a plan is approved. Each approval decision is recorded in the item's activity timeline.

#Plan versions

A work item can have more than one plan. When a plan is rejected, the builder agent writes a new one; the previous version stays in the item's history with a status of rejected. Each plan version carries its own status: submitted, approved, or rejected.

#Submitting a plan

The builder agent drafts and submits a plan automatically after triage. Once submitted, the work item moves to awaiting approval and a pending action appears on your board.

If you create a plan manually using the fallback form on the work item's detail page, submit it the same way to queue it for approval.

#Approve or reject

Open the work item's detail page and scroll to the plan panel. You will see the plan steps and a Reviewer comment field.

• Press Approve plan to accept the plan. The item moves to executing and the builder agent begins the work.
• Press Reject plan to send the item back to planning. The item returns to the planning state and the builder agent writes a revised plan.

A reviewer comment is optional when approving. When rejecting, a comment helps the agent understand what to change in the next version.

#Auto-approval

When a project's trigger policy has approval turned off, plans skip the manual gate. Submitting a plan approves it immediately, the work item moves directly to executing, and no pending action appears on your board.

This setting is per project and is configured in project settings by a project admin.

#Next steps

• Work item states: what happens after a plan is approved and during execution.
• Work the board: where pending plan approvals appear as cards in In Progress.