Skip to main content
A work profile is a preset applied to one task. It sets how much ceremony the agent follows, so a typo fix does not get feature process and an infrastructure change cannot skip the apply gate. A profile has:
  • Gates. planApproval (the agent gets its plan approved before writing code) and reviewBeforePr. Both default on.
  • Test depth. none, smoke, unit or full. Default unit.
  • Expected skills. Skill names the agent is expected to use.
  • Enforce apply gate. For infrastructure-shaped profiles. The code-it-apply gate is stated as mandatory.

How a profile is chosen

In order:
  1. Your explicit pick when you start the agent.
  2. The first auto-select rule that matches the Asana task: its type, a tag, or its status.
  3. The project’s default profile.
  4. None. The workspace renders as it did before profiles existed.
Profiles are open: a project defines its own set. Layered rules (org, team, project, phase) are rendered together into Kiro steering and add up, they do not override each other. Sensors are deterministic checks bound to a profile. See Work profiles and sensors.