From 84c3314924d2d5543c4d36f1505a240c9c8e5944 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sun, 5 Apr 2026 09:47:50 +0200 Subject: [PATCH] fix(skills): sprint-start team branch must not run pr-review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Team worktree windows stay on their sprint branch. PR reviews run from main. Updated step 9b to explicitly stop the team lead from spawning reviewers — push the PR and wait for feedback instead. Co-Authored-By: Claude Opus 4.6 (1M context) --- .claude/skills/sprint-start/SKILL.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/.claude/skills/sprint-start/SKILL.md b/.claude/skills/sprint-start/SKILL.md index d4b48067e..a2af85eb2 100644 --- a/.claude/skills/sprint-start/SKILL.md +++ b/.claude/skills/sprint-start/SKILL.md @@ -512,12 +512,21 @@ When all tasks are complete (TaskList shows all completed): Run `/git-commit` to commit all changes, then `/pr-push` to create or update the PR. Do NOT shut down agents — the team stays alive for review. -#### 9b. Review +#### 9b. Wait for review -Run `/pr-review` to spawn temporary reviewers. Wait for results. +Do NOT run `/pr-review` from the team window — PR reviews run from +the `main` branch (a separate window/session). The team window stays +on its sprint branch. + +After pushing and creating the PR, report the PR number to the user +and stop. Wait for review feedback to arrive (the user or the main +session will relay it, or it will appear as Gitea PR comments). #### 9c. Handle review outcome +When review feedback arrives (from the user, main session, or PR +comments): + **If CHANGES_REQUESTED:** 1. Parse the review comment table (from the Gitea PR comment or the