dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: create 88_story_auto_assign_agents_to_available_work_on_server_startup

Browse Source
This commit is contained in:
Dave
2026-02-23 17:17:49 +00:00
parent 6be3c3fda6
commit 865c3c46f5
1 changed files with 10 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
.story_kit/work/1_upcoming/88_story_auto_assign_agents_to_available_work_on_server_startup.md
View File

@@ -1,23 +1,26 @@
--- ---
name: "Auto-assign agents to available work on server startup" name: "Auto-assign agents to available work"
test_plan: pending test_plan: pending
--- ---
# Story 88: Auto-assign agents to available work on server startup # Story 88: Auto-assign agents to available work
## User Story ## User Story
As a user, I want the server to automatically scan the pipeline on startup and assign agents to any work items that need attention, so that work resumes without manual intervention after a restart. As a user, I want the server to automatically assign free agents to queued work items, both on startup and whenever an agent finishes its current task, so that work progresses continuously without manual intervention.
## Acceptance Criteria ## Acceptance Criteria
- [ ] On server startup, scan work/2_current/ for stories with no running agent and auto-call start_agent for each - [ ] On server startup, scan work/2_current/ for stories with no running coder agent and auto-assign available coders
- [ ] On server startup, scan work/3_qa/ for items with no running QA agent and auto-start the QA agent - [ ] On server startup, scan work/3_qa/ for items with no running QA agent and auto-start the QA agent
- [ ] On server startup, scan work/4_merge/ for items with no running mergemaster agent and auto-start the mergemaster agent - [ ] On server startup, scan work/4_merge/ for items with no running mergemaster agent and auto-start the mergemaster agent
- [ ] When a coder agent completes (moves story to QA), check work/2_current/ for unassigned stories and assign the now-free coder to the next one
- [ ] When a QA or mergemaster agent completes, similarly check their respective queues for more work
- [ ] Auto-assignment respects the agent roster limits from project.toml (don't exceed max concurrent agents per role)
- [ ] Items in work/1_upcoming/ are NOT auto-started (they require explicit user action) - [ ] Items in work/1_upcoming/ are NOT auto-started (they require explicit user action)
- [ ] Auto-assignment respects the agent roster limits from project.toml (don't exceed max concurrent agents) - [ ] Auto-assignment logs clearly which stories are being picked up and which agents are assigned
- [ ] Auto-assignment logs clearly which stories are being resumed and which agents are assigned
## Out of Scope ## Out of Scope
- TBD - Automatic promotion of items from upcoming to current (that remains a user decision)
- Priority ordering of queued work items (FIFO by filename is fine)