## Summary Example: "Developer creates a new work item" **Audit Event Name:** `work_item_created` --- ## Agent Examples ### Agent 1: ### `work_item_created` — Agent Example 2: Autonomous Decomposition & Kickoff **Trigger:** A new work item is created in a project with DAP enabled. **Agent Goal:** Decompose the work item into actionable child issues and autonomously begin implementation without waiting for a human to plan or assign work. **Flow:** 1. A new work item is created with a high-level description — e.g. _"Add SSO support for SAML 2.0"_ 2. The agent analyses the description and breaks it down into smaller, scoped child issues — each with a title, description, and acceptance criteria 3. Child issues are created and appear on the board under the parent work item 4. The agent evaluates the child issues and selects the highest-priority, most self-contained one to begin with 5. The agent moves that child issue to `In Progress` on the board — firing a `work_item_status_changed` trigger 6. Duo Developer kicks off autonomously against that child issue, beginning implementation based on the scoped description ### Agent 2: ### `work_item_created` — Agent Example **Trigger:** A new Issue, Task, or Epic is created in a project with DAP enabled. **Agent Goal:** Ensure the work item is implementation-ready before any human or agent picks it up. **Example Flow:** 1. Work item is created with a title and partial description 2. Agent inspects the work item for completeness — does it have acceptance criteria? An assignee? A milestone? A label? 3. If gaps are found, the agent posts a structured comment surfacing what's missing and optionally kicks off a sync spec co-authoring chat 4. If the work item is sufficiently complete, the agent adds a `spec-ready` label and the item is eligible for the implementation plan step ### --- ## Implementation Notes & Caveats >