crashlabs/huskies
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 26 Wiki Activity

huskies: done 481_bug_scaffold_does_not_copy_agent_definitions_from_project_toml_to_new_projects

Browse Source
This commit is contained in:
dave
2026-04-07 11:26:08 +00:00
parent 89aa705880
commit 018b185489
2 changed files with 5 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.huskies/work/1_backlog/481_bug_scaffold_does_not_copy_agent_definitions_from_project_toml_to_new_projects.md
-33
View File
@@ -1,33 +0,0 @@
---
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
.huskies/work/1_backlog/485_story_documentation_site_for_huskies_dev.md
-27
View File
@@ -1,27 +0,0 @@
---
name: "Documentation site for huskies.dev"
---
# Story 485: Documentation site for huskies.dev
## User Story
As a new user discovering huskies, I want documentation on huskies.dev so I can learn how to set up and use the tool without having to read the source code.
## Acceptance Criteria
- [ ] Docs site lives under website/ directory alongside the existing landing page
- [ ] Accessible from huskies.dev (e.g. huskies.dev/docs/ or docs.huskies.dev)
- [ ] Navigation link added to the main site header
- [ ] Getting started / quickstart guide (Docker setup, first story, first agent run)
- [ ] Configuration reference: project.toml, agents.toml, bot.toml
- [ ] Bot commands reference (auto-generated from command registry or manually maintained)
- [ ] Pipeline stages explained (backlog, current, QA, merge, done)
- [ ] Chat transports guide (Matrix, WhatsApp, Slack, web UI)
- [ ] CLI reference (huskies, huskies init, huskies agent)
- [ ] Matches the visual style of the existing landing page
- [ ] Static HTML — no build step required
## Out of Scope
- TBD