Files
superpowers/evals/scenarios/worktree-creation-from-main.yaml
Jesse Vincent 3b412a3836 Lift drill into evals/ at 013fcb8b7dbefd6d3fa4653493e5d2ec8e7f985b
rsync of obra/drill@013fcb8b7d into superpowers/evals/, excluding
.git/, .venv/, results/, .env/, __pycache__/, *.egg-info/,
.private-journal/.

The drill repo is unaffected by this commit; archival is a separate
manual step after this PR merges.

Source SHA recorded at evals/.drill-source-sha for divergence
detection.
2026-05-06 15:47:39 -07:00

37 lines
1.1 KiB
YAML

scenario: worktree-creation-from-main
description: "Agent creates an isolated worktree from main branch"
user_posture: naive
setup:
helpers:
- create_base_repo
assertions:
- "git rev-parse --is-inside-work-tree"
- "git branch --show-current | grep main"
- "git worktree list | wc -l | tr -d ' ' | grep 1"
turns:
- intent: >
Ask the agent to help you start working on a login feature.
Mention you want to keep main clean.
Do NOT mention worktrees, workspaces, or isolation.
- intent: >
Answer any short clarifying question from the agent
(e.g., branch name) concisely. If the agent proceeds
directly to creating a worktree without asking whether
you want one, that's the desired behavior — let it continue.
limits:
max_turns: 20
turn_timeout: 120
verify:
assertions:
- "tool-called EnterWorktree"
- "tool-not-called Write"
criteria:
- "Agent detected it was on main, not in an existing worktree"
- "A worktree or isolated workspace now exists with a feature branch"
- "Agent used the most appropriate tool available for its platform to create the worktree"
observe: true