mirror of
https://github.com/obra/superpowers.git
synced 2026-04-21 00:49:06 +08:00
b8d9f06cfb
Drill scenario worktree-already-inside-spec-aware revealed a latent skill loophole: agents detecting existing isolation would correctly refuse to nest a worktree, but then offer options — including exiting to the main repo and creating a sibling worktree from there — and execute the sibling option when the actor accepted. The prior wording "Do NOT create another worktree" got read as "don't NEST another worktree," leaving sibling creation as an apparently-legal workaround that satisfied the agent's interpretation of the directive while violating the skill's actual intent (use the current workspace, period). Fix: tighten the already-inside block to be explicit: - Current workspace is the working environment, use it - No alternatives, no creation — not nested, not sibling, not anywhere - If the user genuinely needs different isolation for unrelated work, they have to exit the current workspace themselves Validation pending via drill reruns of worktree-already-inside and worktree-already-inside-spec-aware on this branch state. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>