Ai Droid Sessions And Task Planning

Operator assigns a Droid a multi-file feature task. The Droid begins editing files immediately without surfacing a plan.

Surface a concrete plan (files to touch, order of changes, test strategy) before mutating the working tree, so a human can redirect cheaply. Treat planning as a distinct phase whose output is reviewable; do not collapse plan and execution into one irreversible burst of edits.

After a Droid opens a PR, the operator wants a small change to the same diff. They start a brand-new session pointed at main instead of continuing the existing one.

Continue the existing session/branch when the change is a refinement of the same work, so the Droid keeps the accumulated context (the branch, prior plan, review comments). Start a fresh session only for genuinely new work. Confirm which branch the follow-up targets before editing.

A Droid is told to implement a feature. It commits directly to the default branch instead of a feature branch.

Work on a dedicated feature branch and open a PR/MR for review; never push directly to a protected default branch. Name the branch traceably to the task/ticket. Respect the repo's branch-protection rules rather than working around them.