| 1 | # Developer Agent Profile DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own the bundled software development specialist profile. |
| 6 | - Keep development, debugging, refactoring, and architecture behavior separate from general agent defaults. |
| 7 | |
| 8 | ## Ownership |
| 9 | |
| 10 | - `agent.yaml` owns title, description, and delegation context for software development work. |
| 11 | - `prompts/` owns developer-specific prompt overrides when present. |
| 12 | - `extensions/` owns developer-specific lifecycle hooks when present. |
| 13 | |
| 14 | ## Local Contracts |
| 15 | |
| 16 | - Keep this profile focused on software engineering tasks. |
| 17 | - Do not hardcode repository-local credentials, paths, or project-specific conventions. |
| 18 | - Prompt overrides must preserve the framework tool-call and response contracts. |
| 19 | |
| 20 | ## Work Guidance |
| 21 | |
| 22 | - Align developer behavior with the root engineering and tool contracts. |
| 23 | - Prefer profile prompt edits over core prompt edits when the behavior is specific to development tasks. |
| 24 | |
| 25 | ## Verification |
| 26 | |
| 27 | - Manually inspect `agent.yaml` for valid YAML after edits. |
| 28 | - Run prompt/profile tests when changing profile loading or developer prompt behavior. |
| 29 | |
| 30 | ## Child DOX Index |
| 31 | |
| 32 | No child DOX files. |