Menu
Isolates each dispatch's implementation work in a dedicated git worktree and branch named for the work_id
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Adversarial review gate for scenario-based BC work; sole emitter of work_done for assign_scenarios and bugfix-with-scenarios dispatches
Routes inbound lead messages to the correct BC subagent after sufficiency gating; the sole entry point for all BC inbox processing
Determines whether an inbound lead message is sufficient to act on, or whether a clarify response is required before dispatch
Merges the work branch into the BC's main and pushes so the work_id commit is reachable from origin/main before any work_done emission
Situational mechanics for the turn-limited PO<->Architect BC-decomposition collaboration. Load this when you are actively running a decomposition exchange with the PO (or, as the PO, with the Architect) and need the round cap, the extension protocol, and the ship-from-here rule. Per PDR-014.
Executes a bd-decomposed implementation plan sub-issue by sub-issue with context isolation and mandatory TDD per behavior
Basé sur la classification professionnelle SOC
| name | using-git-worktrees |
| description | Isolates each dispatch's implementation work in a dedicated git worktree and branch named for the work_id |
Every dispatch gets its own worktree and branch. This prevents implementation work for one work_id from bleeding into another and keeps the BC's main clean until the integrating-to-main gate.
The router invokes this skill after the sufficiency check passes and before dispatching to the implementer.
The branch name is derived from the work_id:
bc/<work_id>
Example: work_id shopsystem-auth-abc123 → branch bc/shopsystem-auth-abc123.
From the BC repository root:
git fetch origin
git worktree add .worktrees/<work_id> -b bc/<work_id> origin/main
This creates a worktree at .worktrees/<work_id> — a path inside the BC repository root — checked out to a new branch bc/<work_id> based on origin/main.
Operate only inside the BC root. The worktree path is .worktrees/<work_id> inside the BC repo root — never the parent directory (..). Do not create worktrees in the parent (..), in shared volumes, or at any path outside the BC root.
Why in-root, not ../: a BC runs inside a container where the project root (/workspace) is the bind-mount. Any write outside /workspace trips a hard Claude-Code permission wall — even in bypass mode — and the container root is not writable by the running user. Placing the worktree at .worktrees/<work_id> keeps every write inside /workspace, so the dispatch never stalls on an out-of-project permission prompt.
Pass the worktree path to the implementer subagent. All implementation work (src/, tests/, features/) happens inside this worktree, never on main directly.
When the implementer's work is complete, before invoking the reviewer gate or integrating-to-main:
# In the worktree:
git status --porcelain # must be clean
git log --oneline -5 # confirm commits carry the work_id
Pass the branch name bc/<work_id> to integrating-to-main.
After integrating-to-main completes and work_done is emitted:
git worktree remove .worktrees/<work_id>
git branch -d bc/<work_id>
Remove the worktree and the local branch. The work is now on origin/main; the branch is no longer needed.
digraph worktrees {
rankdir=TB;
suff [label="Sufficiency check passes", shape=box];
create [label="git worktree add\n.worktrees/<work_id>\n-b bc/<work_id> origin/main", shape=box];
impl [label="Implementer works\ninside worktree", shape=box, style=filled, fillcolor="#ccffcc"];
check [label="git status --porcelain\n(must be clean)", shape=diamond];
merge [label="integrating-to-main", shape=box];
clean [label="git worktree remove\ngit branch -d", shape=box];
suff -> create -> impl -> check;
check -> merge [label="clean"];
check -> impl [label="dirty\n(uncommitted work)"];
merge -> clean;
}
Existing branch. If bc/<work_id> already exists (e.g., a prior interrupted session), do not create a new one. Resume from the existing branch:
git worktree add .worktrees/<work_id> bc/<work_id>
Worktree already registered. If git reports the worktree already exists, check whether the work was already completed and the worktree was not cleaned up. Remove the stale worktree with git worktree prune before proceeding.
BC root boundary. All worktree paths must be within the BC repository root (e.g. .worktrees/<work_id>) — never in the parent directory (..), in lead-shop directories, in shared volumes, or at any path outside the project root (/workspace). A containerized BC cannot write outside /workspace; an out-of-project worktree trips a hard permission wall even in bypass mode.