storkit: create 356_story_start_command_should_say_queued_not_error_when_all_coders_are_busy
This commit is contained in:
@@ -1,22 +0,0 @@
|
|||||||
---
|
|
||||||
name: "MCP tools for code search (grep and glob)"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 348: MCP tools for code search (grep and glob)
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a non-Claude agent connected via MCP, I want search tools so that I can find files and search code contents in my worktree.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] grep tool — searches file contents with regex support, returns matching lines with context
|
|
||||||
- [ ] glob tool — finds files by pattern (e.g. '**/*.rs')
|
|
||||||
- [ ] Both scoped to the agent's worktree
|
|
||||||
- [ ] grep supports output modes: content (matching lines), files_with_matches (just paths), count
|
|
||||||
- [ ] grep supports context lines (-A, -B, -C)
|
|
||||||
- [ ] Results limited to prevent overwhelming the LLM context
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
@@ -1,23 +0,0 @@
|
|||||||
---
|
|
||||||
name: "MCP tools for git operations"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 349: MCP tools for git operations
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a non-Claude agent connected via MCP, I want git tools so that I can check status, stage files, commit changes, and view history in my worktree.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] git_status tool — returns working tree status (staged, unstaged, untracked files)
|
|
||||||
- [ ] git_diff tool — returns diff output, supports staged/unstaged/commit range
|
|
||||||
- [ ] git_add tool — stages files by path
|
|
||||||
- [ ] git_commit tool — commits staged changes with a message
|
|
||||||
- [ ] git_log tool — returns commit history with configurable count and format
|
|
||||||
- [ ] All operations run in the agent's worktree
|
|
||||||
- [ ] Cannot push, force-push, or modify remote — server handles that
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
@@ -1,21 +0,0 @@
|
|||||||
---
|
|
||||||
name: "MCP tool for code definitions lookup"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 350: MCP tool for code definitions lookup
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a non-Claude agent connected via MCP, I want a code intelligence tool so that I can find function, struct, and type definitions without grepping through all files.
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] get_definitions tool — finds function/struct/enum/type/class definitions by name or pattern
|
|
||||||
- [ ] Supports Rust (fn, struct, enum, impl, trait) and TypeScript (function, class, interface, type) at minimum
|
|
||||||
- [ ] Returns file path, line number, and the definition signature
|
|
||||||
- [ ] Scoped to the agent's worktree
|
|
||||||
- [ ] Faster than grepping — uses tree-sitter or regex-based parsing
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
@@ -1,18 +0,0 @@
|
|||||||
---
|
|
||||||
name: "Make help command output alphabetical"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 354: Make help command output alphabetical
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a ..., I want ..., so that ...
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] Help command lists bot commands in alphabetical order
|
|
||||||
- [ ] Existing help tests still pass
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
@@ -1,20 +0,0 @@
|
|||||||
---
|
|
||||||
name: "Bot rebuild command to trigger server rebuild and restart"
|
|
||||||
---
|
|
||||||
|
|
||||||
# Story 355: Bot rebuild command to trigger server rebuild and restart
|
|
||||||
|
|
||||||
## User Story
|
|
||||||
|
|
||||||
As a ..., I want ..., so that ...
|
|
||||||
|
|
||||||
## Acceptance Criteria
|
|
||||||
|
|
||||||
- [ ] Matrix bot recognizes `rebuild` as a command
|
|
||||||
- [ ] Command triggers rebuild_and_restart and reports result back to the room
|
|
||||||
- [ ] Command appears in help output
|
|
||||||
- [ ] Build failures are reported to the user without crashing the server
|
|
||||||
|
|
||||||
## Out of Scope
|
|
||||||
|
|
||||||
- TBD
|
|
||||||
@@ -0,0 +1,18 @@
|
|||||||
|
---
|
||||||
|
name: "Start command should say queued not error when all coders are busy"
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 356: Start command should say queued not error when all coders are busy
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a ..., I want ..., so that ...
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] When all coders are busy, 'start' command responds with a short queued message instead of an error
|
||||||
|
- [ ] Message tone is neutral/positive, not a failure message
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user