dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

Update Story Kit workflow docs and move story 26

Browse Source
This commit is contained in:
Dave
2026-02-17 14:12:45 +00:00
parent 5854ff5593
commit d0a1da2176
4 changed files with 34 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
.story_kit/stories/current/26_establish_tdd_workflow_and_gates.md Normal file
View File

@@ -0,0 +1,15 @@
# Story 26: Establish the TDD Workflow and Gates
## User Story
As a user, I want a clear, enforceable TDD workflow with quality gates, so development is test-first and regressions are blocked.
## Acceptance Criteria
- [ ] A test-first workflow is defined and enforced before implementation begins.
- [ ] Each story requires both unit tests and integration tests (standard Rust `tests/` layout).
- [ ] A test plan is produced and approved before any code changes.
- [ ] Stories cannot be accepted unless all required tests pass.
- [ ] Only one failing test is allowed at a time during red-green-refactor.
## Out of Scope
- Backfilling tests for legacy code (covered by a separate story).
- Adding new test frameworks beyond those defined in `specs/tech/STACK.md`.

15
.story_kit/stories/upcoming/26_establish_tdd_workflow_and_gates.md
View File

@@ -1,15 +0,0 @@
# Story 26: Establish the TDD Workflow and Gates
## User Story
As a user, I want a clear, enforceable TDD workflow with quality gates, so development is test-first and regressions are blocked.
## Acceptance Criteria
- A test-first workflow is defined and enforced before implementation begins.
- Each story requires both unit tests and integration tests (standard Rust `tests/` layout).
- A test plan is produced and approved before any code changes.
- Stories cannot be accepted unless all required tests pass.
- Only one failing test is allowed at a time during red-green-refactor.
## Out of Scope
- Backfilling tests for legacy code (covered by a separate story).
- Adding new test frameworks beyond those defined in `specs/tech/STACK.md`.

15
.story_kit/stories/upcoming/31_directory_based_workflow_coordination.md Normal file
View File

@@ -0,0 +1,15 @@
# Story 31: 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.