storkit: accept 378_story_status_command_shows_work_item_type_story_bug_spike_refactor_next_to_each_item
This commit is contained in:
@@ -1,30 +0,0 @@
|
||||
---
|
||||
name: "Web UI implements all bot commands as slash commands"
|
||||
---
|
||||
|
||||
# Story 374: Web UI implements all bot commands as slash commands
|
||||
|
||||
## User Story
|
||||
|
||||
As a user working in the storkit web UI, I want to type slash commands (e.g. `/status`, `/start 42`, `/cost`) in the chat input to trigger the same deterministic bot commands available in Matrix, so that I can manage my project entirely from the browser without needing a chat bot.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] /status — shows pipeline status and agent availability; /status <number> shows story triage dump
|
||||
- [ ] /assign <number> <model> — pre-assign a model to a story
|
||||
- [ ] /start <number> — start a coder on a story; /start <number> opus for specific model
|
||||
- [ ] /show <number> — display full text of a work item
|
||||
- [ ] /move <number> <stage> — move a work item to a pipeline stage
|
||||
- [ ] /delete <number> — remove a work item from the pipeline
|
||||
- [ ] /cost — show token spend (24h total, top stories, by agent type, all-time)
|
||||
- [ ] /git — show git status (branch, uncommitted changes, ahead/behind)
|
||||
- [ ] /overview <number> — show implementation summary for a merged story
|
||||
- [ ] /rebuild — rebuild the server binary and restart
|
||||
- [ ] /reset — clear the current Claude Code session
|
||||
- [ ] /help — list all available slash commands
|
||||
- [ ] Slash commands are handled at the frontend/backend level without LLM invocation
|
||||
- [ ] Unrecognised slash commands show a helpful error message
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
@@ -1,20 +0,0 @@
|
||||
---
|
||||
name: "Status command shows work item type (story, bug, spike, refactor) next to each item"
|
||||
---
|
||||
|
||||
# Story 378: Status command shows work item type (story, bug, spike, refactor) next to each item
|
||||
|
||||
## User Story
|
||||
|
||||
As a user viewing the pipeline status, I want to see the type of each work item (story, bug, spike, refactor) so that I can quickly understand what kind of work is in progress without having to open individual files.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] The status command displays the work item type (story, bug, spike, refactor) as a label next to each item — e.g. "375 [bug] — Default project.toml contains Rust-specific setup commands"
|
||||
- [ ] The type is extracted from the story_id filename convention ({id}_{type}_{slug})
|
||||
- [ ] All known types are supported: story, bug, spike, refactor
|
||||
- [ ] Unknown or missing types are omitted gracefully (no crash, no placeholder)
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- TBD
|
||||
Reference in New Issue
Block a user