Team workflows

A team task should state the intended behavior, constraints, and required checks. Repository instructions can carry conventions that should apply to every run.

Use plan mode for discovery and risky areas, default or acceptEdits for routine local changes, and isolated automation for any non-interactive mode.

Every result should make the changed files, verification commands, failures, and residual risks easy to find. That keeps agent work compatible with the team's existing review process.