From 8973d22afc1be795eb0d4be5a87a9173f8d7d32e Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Feb 2026 15:07:06 +0000 Subject: [PATCH] Renumber upcoming stories and add .ignore updates Drop story 28, renumber 30-33 to 28-31, add story 31 (View Upcoming Stories), and extend .ignore for .claude/ and .story_kit/ directories. Co-Authored-By: Claude Opus 4.6 --- .ignore | 4 +++- ..._standardize_acceptance_tests_and_todos.md | 16 ---------------- ...test_todos.md => 28_ui_show_test_todos.md} | 2 +- ..._directory_based_workflow_coordination.md} | 2 +- ....md => 30_worktree_agent_orchestration.md} | 6 +++--- .../upcoming/31_view_upcoming_stories.md | 19 +++++++++++++++++++ 6 files changed, 27 insertions(+), 22 deletions(-) delete mode 100644 .story_kit/stories/upcoming/28_standardize_acceptance_tests_and_todos.md rename .story_kit/stories/upcoming/{30_ui_show_test_todos.md => 28_ui_show_test_todos.md} (85%) rename .story_kit/stories/upcoming/{31_directory_based_workflow_coordination.md => 29_directory_based_workflow_coordination.md} (86%) rename .story_kit/stories/upcoming/{32_worktree_agent_orchestration.md => 30_worktree_agent_orchestration.md} (96%) create mode 100644 .story_kit/stories/upcoming/31_view_upcoming_stories.md diff --git a/.ignore b/.ignore index 52b0cef..d91f13b 100644 --- a/.ignore +++ b/.ignore @@ -1,2 +1,4 @@ -# Prevents cargo watch from restarting the server when frontend files change +# Prevents cargo watch from restarting the server on non-Rust file changes frontend/ +.claude/ +.story_kit/ diff --git a/.story_kit/stories/upcoming/28_standardize_acceptance_tests_and_todos.md b/.story_kit/stories/upcoming/28_standardize_acceptance_tests_and_todos.md deleted file mode 100644 index 25e297f..0000000 --- a/.story_kit/stories/upcoming/28_standardize_acceptance_tests_and_todos.md +++ /dev/null @@ -1,16 +0,0 @@ -# Story 28: Standardize Acceptance Tests and TODO Flow - -## User Story -As a user, I want a consistent acceptance test layout and TODO workflow, so acceptance criteria are translated into tests in a predictable, toolable way. - -## Acceptance Criteria -- A single, documented folder structure exists for acceptance tests and story TODO files. -- Each story must have a `tests/todo/story-XX.todo` file with one comment per Acceptance Criterion using the format `// AC: story-XX#N - ...`. -- Acceptance tests and integration tests follow the standard Rust `tests/` layout. -- The workflow requires consuming TODOs one at a time: write a failing test, delete the TODO line, make it pass, then refactor. -- The test plan references the frameworks and commands in `specs/tech/STACK.md`. - -## Out of Scope -- Building UI surfaces for TODO visibility. -- Migrating existing tests to the new layout. -- Introducing new test frameworks beyond those listed in `specs/tech/STACK.md`. \ No newline at end of file diff --git a/.story_kit/stories/upcoming/30_ui_show_test_todos.md b/.story_kit/stories/upcoming/28_ui_show_test_todos.md similarity index 85% rename from .story_kit/stories/upcoming/30_ui_show_test_todos.md rename to .story_kit/stories/upcoming/28_ui_show_test_todos.md index 6855bfe..dd3f834 100644 --- a/.story_kit/stories/upcoming/30_ui_show_test_todos.md +++ b/.story_kit/stories/upcoming/28_ui_show_test_todos.md @@ -1,4 +1,4 @@ -# Story 30: Show Remaining Test TODOs in the UI +# Story 28: Show Remaining Test TODOs in the UI ## User Story As a user, I want the UI to show the remaining test TODOs for the current story, so I can track which Acceptance Criteria are still untested. diff --git a/.story_kit/stories/upcoming/31_directory_based_workflow_coordination.md b/.story_kit/stories/upcoming/29_directory_based_workflow_coordination.md similarity index 86% rename from .story_kit/stories/upcoming/31_directory_based_workflow_coordination.md rename to .story_kit/stories/upcoming/29_directory_based_workflow_coordination.md index b8a079a..6addb04 100644 --- a/.story_kit/stories/upcoming/31_directory_based_workflow_coordination.md +++ b/.story_kit/stories/upcoming/29_directory_based_workflow_coordination.md @@ -1,4 +1,4 @@ -# Story 31: Directory-Based Workflow Coordination and Locks +# Story 29: Directory-Based Workflow Coordination and Locks ## User Story As a user, I want directory-based story workflow coordination with lock tracking, so multiple agents can pick up work with minimal context while keeping coordination in `master`. diff --git a/.story_kit/stories/upcoming/32_worktree_agent_orchestration.md b/.story_kit/stories/upcoming/30_worktree_agent_orchestration.md similarity index 96% rename from .story_kit/stories/upcoming/32_worktree_agent_orchestration.md rename to .story_kit/stories/upcoming/30_worktree_agent_orchestration.md index c7f3ae1..1c2e1bd 100644 --- a/.story_kit/stories/upcoming/32_worktree_agent_orchestration.md +++ b/.story_kit/stories/upcoming/30_worktree_agent_orchestration.md @@ -1,4 +1,4 @@ -# Story 32: Worktree-Based Agent Orchestration +# Story 30: Worktree-Based Agent Orchestration ## User Story As a user, I want to press a button in the frontend to spin up an agent that works on a story in its own git worktree, so that multiple stories can be worked on concurrently without branch conflicts. @@ -40,7 +40,7 @@ prompt = "Read .story_kit/README.md, then pick up story {{story_id}}" Components are set up in order. Each `path` is relative to the worktree root. ## Out of Scope -- Coordinating merges to master when multiple agents finish simultaneously (see Story 31). -- Lock file implementation for multi-agent conflict prevention (see Story 31). +- Coordinating merges to master when multiple agents finish simultaneously (see Story 29). +- Lock file implementation for multi-agent conflict prevention (see Story 29). - Port management for dev servers within worktrees. - Agent-to-agent communication. diff --git a/.story_kit/stories/upcoming/31_view_upcoming_stories.md b/.story_kit/stories/upcoming/31_view_upcoming_stories.md new file mode 100644 index 0000000..c2fd7ee --- /dev/null +++ b/.story_kit/stories/upcoming/31_view_upcoming_stories.md @@ -0,0 +1,19 @@ +--- +name: View Upcoming Stories +test_plan: pending +--- + +# Story 31: View Upcoming Stories + +## User Story +As a user, I want to see a list of upcoming stories in the UI so I can understand what work is planned next. + +## Acceptance Criteria +- [ ] The UI displays a panel listing all stories from `.story_kit/stories/upcoming/`. +- [ ] Each story shows its name (from front matter or filename). +- [ ] The list refreshes when the user clicks a refresh button. + +## Out of Scope +- Editing or reordering stories from the UI. +- Showing story details or acceptance criteria inline. +- Moving stories between upcoming/current/archived from the UI.