From b089d314baeeba03d388561bc67499736e6f0121 Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Feb 2026 12:03:22 +0000 Subject: [PATCH] Add user testing step to bug workflow before merge Co-Authored-By: Claude Opus 4.6 --- .story_kit/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.story_kit/README.md b/.story_kit/README.md index 2086a40..fc7f47b 100644 --- a/.story_kit/README.md +++ b/.story_kit/README.md @@ -145,7 +145,8 @@ Not everything needs to be a full story. Simple bugs can skip the story process: 2. **Create a Worktree:** Create a git worktree and branch for the fix (e.g., `git worktree add ../project-bug-N -b bugfix/bug-N-description master`). 3. **Write a Failing Test:** Before fixing the bug, write a test that reproduces it (red). This proves the bug exists and prevents regression. 4. **Fix the Bug:** Make minimal code changes to make the test pass (green). -5. **Archive & Merge:** Move the bug file to `bugs/archive/`, squash merge to master, delete the worktree and branch. +5. **User Testing:** Let the user verify the fix in the worktree before merging. Do not proceed until they confirm. +6. **Archive & Merge:** Move the bug file to `bugs/archive/`, squash merge to master, delete the worktree and branch. 6. **No Guardrail Update Needed:** Unless the bug reveals a missing constraint ### Bug vs Story