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"…
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.
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.
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.
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 agoA59 tokens
originalMIT
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: