story-kit: queue 249_story_agent_assignment_via_story_front_matter for QA
This commit is contained in:
@@ -1,25 +0,0 @@
|
||||
---
|
||||
name: "Agent assignment via story front matter"
|
||||
---
|
||||
|
||||
## Rejection Notes
|
||||
|
||||
**2026-03-16:** Previous coder only updated the serve submodule pointer — no actual implementation. Feature branch also reverted changes from stories 246 and 248. The agent front matter parsing and pipeline assignment logic was never written. Start fresh on a clean branch from master.
|
||||
|
||||
# Story 249: Agent assignment via story front matter
|
||||
|
||||
## User Story
|
||||
|
||||
As a project owner, I want to specify which agent should work on a story via a front matter field (e.g. agent: coder-opus) so that complex stories get assigned to the right coder automatically.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] Story files support an optional agent front matter field (e.g. agent: coder-opus)
|
||||
- [ ] When the pipeline auto-assigns a coder to a story, it uses the agent specified in front matter if present
|
||||
- [ ] If the specified agent is busy, the story waits rather than falling back to a different coder
|
||||
- [ ] If no agent is specified in front matter, the existing default assignment behaviour is used
|
||||
- [ ] The supervisor agent respects the front matter assignment when starting coders
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
Reference in New Issue
Block a user