mirror of
https://github.com/obra/superpowers.git
synced 2026-05-10 02:59:04 +08:00
3b412a3836
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.
35 lines
1.3 KiB
YAML
35 lines
1.3 KiB
YAML
scenario: worktree-creation-from-main-spec-aware
|
|
description: "Agent creates an isolated worktree from main branch on direct skill invocation (spec-aware user)"
|
|
user_posture: spec-aware
|
|
|
|
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 use the worktree skill to get set up
|
|
for building a login 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) 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".
|
|
|
|
limits:
|
|
max_turns: 20
|
|
turn_timeout: 120
|
|
|
|
verify:
|
|
criteria:
|
|
- "Agent detected it was on main, not in an existing worktree"
|
|
- "Agent proceeded to worktree creation without stopping to ask the user whether they wanted a worktree (direct skill invocation is consent)"
|
|
- "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
|