Escape the Dungeon · GAD
escape-the-dungeon/v7
Composite score
0.668
Human review
0.30
Human review note
Game renders, better UI/layout than other evals. But game loop is broken — after combat, player gets stuck with no navigation. Cannot progress past first encounter. UI is bland but structured. Has fallback data (good defensive coding). Score 0.30: renders and partially playable but broken core loop.
Reviewed by human · 2026-04-08
Dimension scores
Where the composite came from
Each dimension is scored 0.0 – 1.0 and combined using the weights in evals/escape-the-dungeon/gad.json. Human review dominates on purpose — process metrics alone can't rescue a broken run.
| Dimension | Score | Bar |
|---|---|---|
| Human review | 0.300 | |
| Requirement coverage | 0.708 | |
| Planning quality | 1.000 | |
| Per-task discipline | 0.810 | |
| Skill accuracy | 0.833 | |
| Time efficiency | 0.950 |
Composite formula
How 0.668 was calculated
The composite score is a weighted sum of the dimensions above. Weights come from evals/escape-the-dungeon/gad.json. Contribution = score × weight; dimensions sorted by contribution so you can see what actually moved the needle.
| Dimension | Weight | Score | Contribution |
|---|---|---|---|
| planning_quality | 0.15 | 1.000 | 0.1500(25%) |
| per_task_discipline | 0.15 | 0.810 | 0.1215(20%) |
| requirement_coverage | 0.15 | 0.708 | 0.1062(18%) |
| human_review | 0.30 | 0.300 | 0.0900(15%) |
| skill_accuracy | 0.10 | 0.833 | 0.0833(14%) |
| time_efficiency | 0.05 | 0.950 | 0.0475(8%) |
| Weighted sum | 0.90 | 0.5985 |
Note: The weighted sum above (0.5985) doesn't exactly match the stored composite (0.6680). The difference is usually the v3 low-score cap (composite < 0.20 → 0.40, composite < 0.10 → 0.25) or a run with an older scoring pass.
Skill accuracy breakdown
Did the agent invoke the right skills at the right moments?
For each expected trigger we recorded whether the agent invoked the skill at the right point in the loop. Accuracy = fired / expected = 0.83.
| Skill | Expected when | Outcome |
|---|---|---|
| /gad:plan-phase | before implementation | fired |
| /gad:execute-phase | per phase | fired |
| /gad:task-checkpoint | between tasks | fired |
| /gad:auto-conventions | after first code phase | fired |
| /gad:verify-phase | after phase completion | fired |
| /gad:check-todos | session start | missed |
What the agent built for itself
Emergent workflow artifacts
Bare and emergent runs don't have a framework giving them structure — they author their own methodology on the fly. These are the files the agent wrote into its own game/.planning/during this run. When a file appears here that isn't in the inherited bootstrap set, the agent invented it.
Planning notes(2)
ARCHITECTURE.md3.3 KBVERIFICATION.md1022 B
Gate report
Requirement coverage
Reviewer notes on gates
Game renders, title screen works, combat works. But game loop breaks — after combat, player is stuck with no route back to room navigation.
Process metrics