From 2eddff6642cba77b39d665b83e80c280b4d5a66c Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 14:09:27 +0000 Subject: [PATCH] story-kit: remove 29_story_directory_based_workflow_coordination --- ...y_directory_based_workflow_coordination.md | 19 ------------------- 1 file changed, 19 deletions(-) delete mode 100644 .story_kit/work/1_upcoming/29_story_directory_based_workflow_coordination.md diff --git a/.story_kit/work/1_upcoming/29_story_directory_based_workflow_coordination.md b/.story_kit/work/1_upcoming/29_story_directory_based_workflow_coordination.md deleted file mode 100644 index 4d2de87..0000000 --- a/.story_kit/work/1_upcoming/29_story_directory_based_workflow_coordination.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -name: Directory-Based Workflow Coordination and Locks -test_plan: pending ---- -# 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`. - -## Acceptance Criteria -- Add a `stories/check/` directory for review/verification handoff. -- Define a lock file format in `master` (e.g., `.story_kit/locks.json`) that tracks story assignment, agent identity, worktree path, and last update time. -- Document the story lifecycle across `upcoming/`, `current/`, `check/`, and `archived/` directories. -- Document that code changes happen in worktrees, while coordination files and story movement live in `master`. - -## Out of Scope -- Implementing the lock mechanism or agents in code. -- Enforcing locks at runtime. -- Multi-agent orchestration beyond documenting the workflow.