Quantified sprint metrics for AI-assisted development. Scorecards, handicap tracking, and real-time agent guidance for Claude Code, Cursor, Windsurf, Cline, and OpenCode.
Package Exports
@slope-dev/slope
@slope-dev/slope/adapters
@slope-dev/slope/store-pg
Readme
SLOPE
Sprint Lifecycle & Operational Performance Engine
Replace subjective retrospectives with quantified sprint metrics. Track every ticket's approach, outcome, and hazards — then use rolling analytics to spot patterns and improve over time.
Why SLOPE?
Quantified retros — structured scorecards with objective scoring instead of "how did it feel?"
Pattern detection — rolling handicap windows reveal if you consistently over-engineer, under-scope, or pick the wrong approach
AI agent guidance — 16 guard hooks give real-time hints to Claude Code, Cursor, Windsurf, Cline, and OpenCode
Pluggable metaphors — golf, tennis, baseball, gaming, D&D, matrix, or agile terminology — same math, your vocabulary
Zero infrastructure — SQLite store, CLI-driven, lives in your repo
Quick Start
# Installnpminstall-g @slope-dev/slope
# Initialize (auto-detects your AI coding tool)
slope init
# View your handicap card
slope card
Installed locally? Use npx slope instead.
Core Concepts
Every sprint has a par (expected baseline from ticket count: 1–2 → par 3, 3–4 → par 4, 5+ → par 5). Each ticket is a shot with an approach complexity (club: driver → putter) and an outcome (result: in_the_hole → missed). Over time, your handicap card shows rolling averages, miss patterns, and trend direction.