srbryers/slope

SLOPE — Sprint Lifecycle & Operational Performance Engine. Golf-metaphor sprint scoring for engineering teams.

This repository also configures its own agents. See what slope tells them →

6Stars on the repository
25Mods indexed here, across every type
8d agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

slope-loop-guide

01

srbryers/slope

Skill Claude CodeCodex

Institutional knowledge for the Slope autonomous development loop. Use when executing automated sprints, reviewing loop results, analyzing model tier performance, or working on Slope's own codebase via the loop. Use when user says "run a sprint", "check loop status", "review sprint results", "model performance"…

not rated 6 8d ago A 107 tokens original MIT

slope-guard-warning

02

srbryers/slope

Skill Claude CodeCodex

Respond to SLOPE guard warnings in Codex without bypassing sprint discipline. Trigger when a SLOPE guard warns, blocks, recommends a review, asks for a claim, or reports missing sprint context.

not rated 6 8d ago A 48 tokens original MIT

slope-retro

03

srbryers/slope

Skill Claude CodeCodex

Run SLOPE post-merge retros from Codex and persist durable learnings. Trigger after a pull request merges, when the user asks for a retro, or when sprint closeout should save lessons into memory.

not rated 6 8d ago A 48 tokens original MIT

slope-setup

04

srbryers/slope

Skill Claude CodeCodex

Set up SLOPE in a Codex-managed repository without requiring the user to know CLI details. Trigger when the user asks to install, initialize, update, or verify SLOPE for Codex.

not rated 6 8d ago A 46 tokens original MIT

slope-sprint

05

srbryers/slope

Skill Claude CodeCodex

Use SLOPE from Codex to inspect, start, claim, or close a sprint in a repository with .slope state. Trigger when the user asks to set up SLOPE, register sprint work, check active sprint status, or close out sprint work.

not rated 6 8d ago A 59 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: