@verbose_explorer’s amp summary

personal reference distilled from 94 insight files across 4,656 threads.

NUMBERS (CORRECTED)

metric	@verbose_explorer	comparison
resolution rate	83%	top tier (@precision_pilot: 82.2%)
avg turns	39.1	efficient (@concise_commander: 86.5)
handoff rate	4.2%	low (@concise_commander: 13.5%)
spawned subagents	231	97.8% success
steering/thread	0.28	@concise_commander: 0.81
approvals/thread	0.55	@concise_commander: 1.54

correction note: prior analysis miscounted spawned subagent threads (“Continuing from thread…”) as HANDOFF, deflating resolution to 33.8% and inflating handoff to 29.7%.

PATTERNS

spawn orchestration

231 spawned subagents with 97.8% success. effective parallelization of work.

file references

@path/to/file in opener → +25% success (66.7% vs 41.8%). single strongest predictor in the data.

long thread commitment

78% resolution at 100+ turns. sustained engagement correlates with resolution.

domain expertise

nix work: 70% success rate. meta-work (skills, tooling, infrastructure): successful threads cluster here.

OBSERVATIONS

approval frequency

0.55 approvals/thread vs @concise_commander’s 1.54. @verbose_explorer’s higher resolution rate (83% vs 60.5%) suggests approval frequency may not be the limiting factor it appears.

evening patterns (uncertain)

19:00-22:00: lower resolution rates observed.

caveat: may reflect task type selection (exploratory work) rather than reduced effectiveness. insufficient evidence for causal claim.

REFERENCE: THREAD STRUCTURE

┌─────────────────────────────────────────────────────────────────┐
│ OPENER PATTERNS                                                 │
│ • file references (@path/to/file): +25% success                 │
│ • 300-1500 chars typical for successful threads                 │
│ • steering question as opener: 71.4% resolution                 │
├─────────────────────────────────────────────────────────────────┤
│ SPAWNING                                                        │
│ • include: goal, constraints, expected output, reference files  │
│ • 97.8% success rate on 231 spawned agents                      │
├─────────────────────────────────────────────────────────────────┤
│ CLOSING                                                         │
│ • explicit "ship it" or "commit" correlates with shorter        │
│   COMMITTED threads (40% shorter than average)                  │
└─────────────────────────────────────────────────────────────────┘

SUCCESSFUL THREAD EXAMPLES

T-048b5e03 — debugging migration (988 turns, 14 approvals) → RESOLVED
T-5ac8bb63 — coordinate sub-agents (466 turns, 13 approvals) → RESOLVED
T-c7c1489c — refactor list component (433 turns, 3 approvals) → RESOLVED
T-40f50ba9 — pnpm global install on NixOS (32 turns, 3 approvals, 0 steerings) → RESOLVED

pattern: complex work, sustained engagement, periodic approvals, minimal steering.

WARNING SIGNS (OBSERVED IN FRUSTRATED THREADS)

only 2 frustrated threads across 875 total:

signal	observed pattern
approval:steering < 1:1	both frustrated threads had low approval counts
thread > 100 turns, no resolution	one frustrated thread ran 160 turns

DATA SUMMARY

metric	value
total threads	875
resolution rate	83%
spawned subagents	231
spawn success rate	97.8%
handoff rate	4.2%
frustrated threads	2

distilled from 94 insight files | 4,656 threads | 208,799 messages | corrected 2026-01-09