Skip to main content
Work profiles, layered rules and sensors live in the project editor under Agent. All three are off until configured, and an unconfigured project renders the same workspace as before.

Work profiles

Define presets, optional auto-select rules and a default.
  • Preset: slug, name, description, gates (planApproval, reviewBeforePr), test depth (none, smoke, unit, full), expected skills, and enforce apply gate.
  • Rule: when the Asana task’s type, tag or section equals a value, use a profile. First match wins, so put the specific rules first.
  • Default profile: used when nothing else matched.
When you start an agent, the Work profile field appears in the New agent dialog if the project defines presets. Your pick beats a rule, and a rule beats the default.

Layered rules

Org, team, project and phase rule sets. Every enabled layer is rendered into its own numbered Kiro steering file. Layers add up. A more specific layer never silently replaces a broader one.

Sensors

Sensors are deterministic checks bound to a profile and rendered as Kiro hooks. Each is advisory (records the finding) or blocking (refuses the action). The library is fixed: Over MCP: get_code_it_work_profiles and set_code_it_work_profiles.