AI agents don't learn from their mistakes.
SLOPE changes that.
A sprint scoring framework — inspired by golf — that turns every AI agent session into measurable, improvable data.
AI Agents Are Powerful. But Chaotic.
Without structure, agent sprints become unpredictable. Work gets lost. Patterns repeat. Nobody knows if the team is improving.
ERROR: Agent crashed mid-sprint, no recovery point
$ git log --oneline | wc -l → 47 commits, no pattern
WARN: Same bug as 3 sprints ago
$ how many tests? → "not sure, maybe 200?"
ERROR: Context lost on compaction
$ what improved? → "hard to say"
... (scrolls for 500 more lines)
Sprint 175 — Par 3 — Score: 3 (Par)
Fairways: 3/3 (100%) | GIR: 3/3 (100%)
Hazards: 1 (ordering bug) — logged & recoverable
Handicap trending: 2.1 → 1.2 (last 5)
Miss pattern: long (43%) — training focus set
Next: guided by yardage book + hazard map
The Framework
Five dimensions. One scoring system.
Each letter maps to a measurable aspect of sprint execution. Together they create a complete picture of agent performance.
Sprint Lifecycle
Every sprint is a hole with a par. Ticket count determines expected difficulty. Score against par, not against perfection.
1-2 tickets = Par 3 | 3-4 tickets = Par 4 | 5+ tickets = Par 5 Leverage
Club selection maps to approach complexity. A driver for risky new infrastructure. A putter for trivial fixes. Declare your club before the shot.
Driver → Long Iron → Short Iron → Wedge → Putter Operational Performance
Track hazards hit, miss directions, and penalties. Every gotcha gets logged. Patterns emerge from data, not memory.
Fairway % | GIR % | Putts | Penalties | Miss Direction Predictive Engine
Rolling handicap averages predict future performance. Last-5 and last-10 windows show trajectory. Getting better or worse?
Handicap = avg(score - par) over rolling window Execution Routines
Pre-shot, post-shot, and 19th hole routines ensure nothing is skipped. Every sprint starts with the yardage book. Every ticket ends with scoring.
Pre-Round → Pre-Shot → Execute → Post-Shot → 19th Hole The Metaphor
Why Golf?
Golf is the only sport where you compete against yourself and the course — not an opponent. Software development is the same.
SLOPE borrows golf's vocabulary because it maps perfectly: known difficulty (par), personal benchmarking (handicap), hazard tracking (bunkers), and structured routines (pre-shot, post-shot) that elite players use to improve consistently.
The Par System
Know your difficulty before you start. Par is determined by ticket count. Slope factors add terrain difficulty on top.
Slope Factors (each adds +1 difficulty)
The Shot Cycle
Every ticket follows a routine. Preparation, execution, and review — so nothing falls through the cracks.
Pre-Shot
Before writing code
Execute
Writing code
Post-Shot
After completing a ticket
The Scorecard
Real data from real sprints. Every scorecard is computed automatically from ticket outcomes — no manual counting.
| Sprint | Theme | Par | Score | Result |
|---|---|---|---|---|
| #175 | demo exploration | 3 | 3 | Par |
| #174 | guided first-project | 3 | 4 | Bogey |
After 175 sprints
Every hazard logged. Every miss direction tracked. The framework doesn't just measure — it teaches.
The Hazard Map
Track what trips you up. Every hazard is categorized, logged, and mapped so future sprints can avoid the same traps.
A known issue logged in previous sprints. Sand trap — recoverable but costly.
Drop a stroke. Breaking changes force rework and downstream fixes.
Out of bounds. Work that extends beyond the ticket boundary.
Playable but slower. Existing debt that drags down execution speed.
Can't take a direct shot. Dependencies that force detours.
Miss Direction Pattern
The 19th Hole
In golf, the 19th hole is where you sit down after the round and talk about what happened. In SLOPE, it's where improvement actually happens.
Post-Round Reflection
What the Data Teaches
When most misses go long, sprints are being underestimated. The fix: tighter scoping, more wedge shots, fewer drivers.
Consistent routines compound. The yardage book gets richer every sprint. Bunker locations prevent repeat mistakes.
Start Scoring Your Sprints
SLOPE is open methodology. Read the framework, adopt what fits, and start turning your agent sessions into measurable progress.
Development Progress
SLOPE is the development methodology behind CaddyStack — a conversational AI platform for managing coding agents.
Built with Astro, Tailwind, and GSAP. Stats from the live CaddyStack API.