Open Source Sprint Scoring

AI agents don't learn from their mistakes.

AI agents can write code, run tests, and ship features. But they start every session from scratch — no memory of what worked, what failed, or what to do differently.

SLOPE gives them a framework that produces data humans can actually use.

28 sprints and counting
See how it works

AI Agents Are Powerful. But Chaotic.

Without structure, session 50 looks exactly like session 1. SLOPE is designed around the three constraints that make AI agents unreliable at scale.

Context loss

Agents crash, compact, and restart from zero. Everything they learned last session is gone.

No consistency

Every session is ad-hoc. Quality depends on luck, not process. The agent might check tests, might not.

No improvement

Same mistakes, same blind spots, no trends. No data to tell you if things are getting better or worse.

How SLOPE Solves This

1

Plan

Briefing reads from disk — scorecards, hazard maps, codebase context. The agent starts informed, not blank.

solves: context loss

2

Execute

Fixed routines at every stage. Same steps, same order. Automated guards catch common mistakes before they land.

solves: inconsistency

3

Score + Learn

Every sprint produces a scorecard. Rolling stats build a performance index. Miss patterns and hazard maps feed back into the next Plan.

solves: no improvement

loops back to Plan

Sprint 1 plans blind. Sprint 50 plans with 49 sprints of structured data.

See It In Action

The difference is data.

Without SLOPE, you get a wall of text. With SLOPE, you get structured output — a scorecard, stats, and a clear next step. Switch the vocabulary to see it in your team's language.

Without SLOPE

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)

With SLOPE

── Hole 28 ────────────────────

"User Auth & Session Management" │ Par 4

# Shot Club Result Hz
S28-1 Add login endpoint Wedge Green
S28-2 JWT token flow Short Iron Fairway
S28-3 Session middleware Long Iron Bunker 1
S28-4 Auth guard tests Putter Hole!

Score: 4 (Par) │ Handicap: 1.2

FW: 100% · GIR: 75% · Putts: 0.25

Hole complete. What next?

Plan a new hole
Refine the backlog
Cleanup / bug fix

One Framework, Six Languages

Same engine. Different vocabulary.

The scoring engine doesn't change — only the language does. Pick the metaphor your team already understands.

Scorecard Hole 28
Par 4 | Score: 4 (Par)
1 Setup & config
Wedge Green
2 Core feature implementation
Short Iron Fairway
3 Integration + edge cases
Long Iron Bunker
4 Tests & documentation
Putter In the Hole
Fairways: 4/4 GIR: 3/4 Putts: 1 Handicap: 1.2
Concept Metaphor Term
SprintHole
TicketShot
ScorecardScorecard
Performance CardHandicap Card
BriefingPre-round Briefing
Perfect ScoreHole-in-one
On TargetPar
Review19th Hole
High-risk approachDriver
Precision approachWedge
Known gotchaBunker
Breaking changeWater
Scope creepOut of Bounds

It Works

Consistent routines compound.

94 %

Estimation Accuracy

How often sprint scoping is on target

75 %

Delivery Accuracy

How often tickets land as planned

1.2

Performance Index

Overall rating (lower is better)

In Sprint 12, the same bug appeared for the third time. SLOPE flagged it as a recurring hazard. It never appeared again.

Every metric on this page comes from the reference implementation — 28 sprints of real work.

Quick Start

Four steps. First sprint.

Get started with CLI commands or natural language prompts. Same flow, your choice.

$ npm install -g @srbryers/cli
1
slope init

Initialize

Set up SLOPE in your project. Pick a metaphor. Configure guards.

2
slope briefing

Get briefed

Get a pre-sprint briefing: risk index, performance snapshot, known issues.

3
slope card

Check your card

Check your performance card — rolling stats across multiple windows.

4
slope review

Review the sprint

Generate a sprint review with ticket-by-ticket analysis and improvement recommendations.

Go Deeper

Ready to score your sprints? Start with the CLI. Want the full technical breakdown? Read the framework.

Start scoring your sprints

$ npm install -g @srbryers/cli

Then run slope init in your project

Read the full framework

Scoring engine, metaphor system, guards, routines, and the complete methodology.

The SLOPE Framework

@srbryers/core · @srbryers/cli · @srbryers/tokens · @srbryers/mcp-tools

SLOPE is an open-source sprint scoring framework for AI agent teams.

Built with Astro, Tailwind, and GSAP. Live stats from the reference implementation.