huskies: create 481_bug_scaffold_does_not_copy_agent_definitions_from_project_toml_to_new_projects

.huskies/work/1_backlog/481_bug_scaffold_does_not_copy_agent_definitions_from_project_toml_to_new_projects.md

@@ -0,0 +1,33 @@
+---
+name: "Scaffold does not copy agent definitions from project.toml to new projects"
+---
+
+# Bug 481: Scaffold does not copy agent definitions from project.toml to new projects
+
+## Description
+
+When scaffolding a new project with `huskies init`, the `[[agent]]` definitions from huskies' own `project.toml` are not included in the new project's config. The scaffold generates a minimal `project.toml` with basic settings (default_qa, max_coders, etc.) but no agent blocks.
+
+Without agent definitions (prompts, system prompts, model, max_turns, budget), the agents run with no guidance — they don't know about the SDTW process, worktrees, feature branches, or the rule about not committing to master. Result: agents make changes directly in master.
+
+The scaffold should include the battle-tested agent definitions (coder, QA, mergemaster) with their prompts and system prompts so new projects get sensible agent behaviour out of the box.
+
+## How to Reproduce
+
+1. Run `huskies init` on a new project
+2. Check the generated `.huskies/project.toml`
+3. Note: no `[[agent]]` blocks present
+4. Start a coder agent on a story
+5. Agent works directly in master with no worktree, no feature branch, no process
+
+## Actual Result
+
+No agent definitions in scaffolded project.toml. Agents run with defaults and make changes directly in master.
+
+## Expected Result
+
+Scaffolded project.toml includes default agent definitions (coder, QA, mergemaster) with prompts that enforce the SDTW process, worktrees, and feature branches.
+
+## Acceptance Criteria
+
+- [ ] Bug is fixed and verified