---
name: "Story dependencies in pipeline auto-assign"
---

# Story 484: Story dependencies in pipeline auto-assign

## User Story

As a user creating stories that depend on each other, I want to specify dependencies in the story front matter so dependent stories stay in backlog until their dependencies are done, then automatically move to current.

Stories with `depends_on` stay in backlog. A dependency check loop (similar to the timer tick) periodically scans backlog for stories whose dependencies have all reached done/archived. When all deps are met, the story is moved to current and the normal auto-assign picks it up — ensuring the worktree is created from post-dependency master.

## Acceptance Criteria

- [ ] New optional `depends_on` field in story front matter accepts a list of story numbers (e.g. `depends_on: [477, 478]`)
- [ ] Stories with unmet dependencies stay in **backlog**, not current
- [ ] A dependency check loop (similar to the timer tick loop) periodically scans backlog for stories whose `depends_on` stories have all reached done or archived
- [ ] When all deps are met, the loop moves the story from backlog to current — the normal auto-assign then picks it up with a worktree based on post-dependency master
- [ ] Status command shows dependency info for stories waiting on deps
- [ ] Stories with no depends_on field behave as before (no change)
- [ ] Bot command `depends <number> <dep1> [dep2...]` to set dependencies from chat (all transports) and web UI slash command
- [ ] Command wired up in bot_command.rs dispatch for web UI and registered in shared command registry for all chat transports

## Out of Scope

- TBD
