Playbook 07: the check counts milestone issues only (issue 1007, review round 1)

2026-10-17 13:23:21 +02:00
parent 974b3e7d42
commit 88d7db36c8
1 changed files with 1 additions and 1 deletions
@@ -254,7 +254,7 @@ issues in `fixing` that nobody works on reads to the operator as stuck work.
  phase 1, is the failure this playbook prevents.
 - A context file exists per touched repository under `.work/<slug>/` while the feature runs.
 - After a feature's delivery, `git branch -r | grep feat/<slug>` and `git worktree list` return nothing for it.
- The issues in `fixing` (`issue-tracker.list`) belong to the milestones of one design at most: milestone issues
+- The milestone issues in `fixing` (`issue-tracker.list`) belong to one design at most: milestone issues
  of two designs in `fixing` at once is the failure of "one design is built at a time".
 - More than one open pull request in a repository that share no feature name, or a feature step whose issues
  stay in `fixing` for more than a working day, is the smell: stop and bring it to the operator.