From 5805d17f0bedb657713672368f7803df8a911d12 Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Wed, 11 Feb 2026 23:31:10 +0100 Subject: [PATCH] chore(skills): require plan mode in start-sprint skill Replace immediate ticket status change with a mandatory plan mode step. Agent must now enter plan mode, create a concrete sprint plan covering implementation approach and ticket ordering, and get user approval before marking any ticket as in_progress. Co-Authored-By: Claude Opus 4.6 --- .claude/skills/start-sprint/SKILL.md | 28 ++++++++++++++++++++++++---- 1 file changed, 24 insertions(+), 4 deletions(-) diff --git a/.claude/skills/start-sprint/SKILL.md b/.claude/skills/start-sprint/SKILL.md index a2b59e72a..2aaf2df40 100644 --- a/.claude/skills/start-sprint/SKILL.md +++ b/.claude/skills/start-sprint/SKILL.md @@ -95,7 +95,27 @@ Output a summary: - Key decisions loaded - Suggested first task (lowest ID unblocked ticket) -Then mark the first actionable ticket as `in_progress`: -```bash -"$REPO_ROOT/db/connectors/ticket" status in_progress -``` +Do NOT mark any ticket as `in_progress` yet. + +### 8. Enter plan mode + +After presenting the work plan summary, you MUST enter plan mode using the +`EnterPlanMode` tool. In plan mode: + +1. **Create a concrete sprint plan** — for each actionable ticket, outline: + - What files need to be created or modified + - What the implementation approach is + - What order tickets should be tackled in (respecting dependencies) + - Any open questions or risks per ticket + +2. **Include blocked tickets** — note what unblocks them and when they might + become actionable during the sprint. + +3. **Write the plan to the plan file** — the plan should be self-contained so + you can follow it step-by-step once approved. + +4. **Exit plan mode** — use `ExitPlanMode` to present the plan for user + approval before starting any implementation work. + +Only after the user approves the plan should you mark the first ticket as +`in_progress` and begin implementation.