Files
superpowers/evals/scenarios/worktree-consent-flow.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

33 lines
1.1 KiB
YAML

scenario: worktree-consent-flow
description: "Agent treats direct skill invocation as consent and proceeds to create a worktree"
user_posture: spec-aware
setup:
helpers:
- create_base_repo
assertions:
- "git rev-parse --is-inside-work-tree"
- "git branch --show-current | grep main"
turns:
- intent: >
Ask the agent to use the worktree skill to get set up
for a notifications feature. Do NOT say "create a worktree"
— just reference the skill by name.
- intent: >
Answer any short clarifying question from the agent (e.g.,
branch name or location) concisely. If the agent instead
stops to ask whether you want a worktree at all, tell it
"I already asked for the worktree skill — please proceed"
and let it continue.
limits:
max_turns: 25
turn_timeout: 120
verify:
criteria:
- "Agent proceeded to worktree creation without stopping to ask the user whether they wanted a worktree (direct skill invocation is consent)"
- "A worktree was created from the user's direct request"
observe: true