From 3ca12e33a3dea4b32851f1c23a3e1c06b605722a Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Wed, 18 Feb 2026 11:59:06 +0100 Subject: [PATCH] feat(skills): start-sprint marks actionable tickets in_progress MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Step 7 now transitions all unblocked sprint tickets to in_progress immediately rather than deferring to agents (who forget). Completes the ticket lifecycle: start-sprint → in_progress, push-pr → review, sprint stop → done. Co-Authored-By: Claude Opus 4.6 --- .claude/skills/start-sprint/SKILL.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/.claude/skills/start-sprint/SKILL.md b/.claude/skills/start-sprint/SKILL.md index 541175d12..1cd236ec9 100644 --- a/.claude/skills/start-sprint/SKILL.md +++ b/.claude/skills/start-sprint/SKILL.md @@ -131,18 +131,23 @@ db/connectors/ticket show Read the decision files referenced in the sprint briefing so the agent has full architectural context before starting work. -### 7. Present the work plan +### 7. Mark tickets in progress and present the work plan -Output a summary: +Mark all actionable (unblocked, non-done) tickets in the sprint as +`in_progress`: + +```bash +db/connectors/ticket status in_progress +``` + +Then output a summary: - Sprint name and goal - Branch status (clean merge or conflicts) -- Actionable tickets (unblocked, ready to start) +- Tickets marked in_progress (list with IDs) - Blocked tickets (and what blocks them) - Key decisions loaded - Suggested first task (lowest ID unblocked ticket) -Do NOT mark any ticket as `in_progress` yet. - ### 8. Confirm and spawn the team Before spawning agents, use `AskUserQuestion` to confirm the work plan and