From c85d02a3efe74e2fb92af07dee092a517a1cf954 Mon Sep 17 00:00:00 2001 From: Dave Date: Wed, 18 Mar 2026 14:33:11 +0000 Subject: [PATCH] story-kit: done 287_story_rename_upcoming_pipeline_stage_to_backlog --- ...name_upcoming_pipeline_stage_to_backlog.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 .story_kit/work/5_done/287_story_rename_upcoming_pipeline_stage_to_backlog.md diff --git a/.story_kit/work/5_done/287_story_rename_upcoming_pipeline_stage_to_backlog.md b/.story_kit/work/5_done/287_story_rename_upcoming_pipeline_stage_to_backlog.md new file mode 100644 index 0000000..4b6b80c --- /dev/null +++ b/.story_kit/work/5_done/287_story_rename_upcoming_pipeline_stage_to_backlog.md @@ -0,0 +1,22 @@ +--- +name: "Rename upcoming pipeline stage to backlog" +--- + +# Story 287: Rename upcoming pipeline stage to backlog + +## User Story + +As a project owner, I want the "upcoming" pipeline stage renamed to "backlog" throughout the codebase, UI, and directory structure, so that the terminology better reflects that these items are not necessarily coming up next. + +## Acceptance Criteria + +- [ ] Directory renamed from 1_upcoming to 1_backlog +- [ ] All server code references updated (watcher, lifecycle, MCP tools, workflow, etc.) +- [ ] Frontend UI labels updated +- [ ] MCP tool descriptions and outputs use "backlog" instead of "upcoming" +- [ ] Existing story/bug files moved to the new directory +- [ ] Git commit messages use "backlog" for new items going forward + +## Out of Scope + +- TBD