From 91130738069b6217dc4480e1fd08014ac195c507 Mon Sep 17 00:00:00 2001 From: Pierre Brisorgueil Date: Thu, 11 Jun 2026 14:25:36 +0200 Subject: [PATCH] chore(skills): /feature claim flips board status to In progress MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Phase 0.0 step 3b — best-effort call to infra's board-status.sh after a successful claim (bubbles sub-issue flips to the parent epic). Silent no-op off-machine / boardless org; /dev:roadmap in-progress-sync is the safety net. --- .claude/skills/feature/SKILL.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/.claude/skills/feature/SKILL.md b/.claude/skills/feature/SKILL.md index d078fc54f..9e8b19316 100644 --- a/.claude/skills/feature/SKILL.md +++ b/.claude/skills/feature/SKILL.md @@ -53,6 +53,17 @@ gh issue comment --body "WIP — session $(date -u +%Y%m%dT%H%M%SZ)-$(uuidge Where `` is the branch this `/feature` invocation will use (planned name, even if not yet created). If the branch isn't decided yet, use `branch TBD`. Posting a follow-up comment with the real branch name after `/pull-request` creates it is best-effort manual — the linked PR superseding the WIP comment is what matters in practice. +### 3b. Board status → In progress (best-effort) + +After a successful claim, flip the issue's board item — and, if it's a sub-issue, its parent epic — to **In progress**: + +```bash +_bs=/Users/pierrebrisorgueil/Documents/Dev/github/pierreb-projects/infra/marketplace/shared/board-status.sh +[ -f "$_bs" ] && bash "$_bs" "$(gh repo view --json nameWithOwner -q .nameWithOwner)#" "In progress" || true +``` + +Best-effort by design: script missing (machine without the infra checkout), org without a board (comes/montaine), or issue not yet on the board → silent no-op; `/dev:roadmap` in-progress-sync is the safety net. Never set Ready or Done from here. + ### 4. Proceed to Phase 0 Continue to scope analysis below.