What is slope-sprint-checklist?

A checklist system for managing the stages of a SLOPE sprint, from roadmap preparation through ticket work and wrap-up.

Use it to compile and validate roadmaps, review scope and bottlenecks, discover the next action, and load focused sprint context before coding.

It provides repeatable checks for dependencies, roadmap gaps, current work, project context, testing, APIs, and session continuity.

slope-sprint-checklist — Cursor rule for Cursor by srbryers

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/srbryers/slope

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/srbryers/slope/slope-sprint-checklist.svg)](https://agentmods.dev/rules/srbryers/slope/slope-sprint-checklist)

Your own site

<a href="https://agentmods.dev/rules/srbryers/slope/slope-sprint-checklist"><img src="https://agentmods.dev/badge/rules/srbryers/slope/slope-sprint-checklist.svg" alt="Measured on agentmods" height="20"></a>

Per session 682 This file is loaded in full into every session.

When invoked 682 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00682	$0.00682
Opus 5	$0.00341	$0.00341
Sonnet 5	$0.00136	$0.00136
Haiku 4.5	$0.00068	$0.00068

Measured 7d ago against content hash aa1d77bfa796, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

slope-sprint-checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

templates/cursor/rules/slope-sprint-checklist.mdc · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Sprint Checklists (SLOPE Routine Hierarchy)

The SLOPE framework organizes sprint work into a hierarchy of routines, mirroring golf's structured approach to each shot, hole, and round.

Pre-Tournament Routine (Course Strategy)

Before starting a new phase or project:

Build the roadmap — Edit declared YAML bundles when docs/roadmap/project.yaml exists; otherwise create docs/backlog/roadmap.json
Compile modular sources — Run slope roadmap compile, slope roadmap validate-sources, and slope roadmap compile --check
Run slope roadmap validate — Check for dependency cycles, numbering gaps
Run slope roadmap review — Scope balance, critical path, bottlenecks
Run slope roadmap show — Dependency graph and parallel tracks

Pre-Round Routine (Sprint Start)

Before writing any code in a new sprint:

Run slope now — Discover the current sprint and next action
Run slope roadmap focus --sprint=N — Use the discovered sprint to load bounded context before full history
Run slope briefing — Outputs handicap snapshot, hazard index, nutrition alerts, filtered gotchas, and session continuity
- Use --categories=testing,api or --keywords=migration to filter for the sprint's work area
Verify previous scorecard exists — If the last sprint's scorecard wasn't created, create it now
Branch hygiene check — git branch -a to confirm no stale branches remain
Set par and slope — Par from ticket count (1-2=3, 3-4=4, 5+=5), slope from complexity factors

Pre-Shot Routine (Per-Ticket, Before Code)

Select your club — driver (risky/new), long_iron (multi-package), short_iron (standard), wedge (small), putter (trivial)
Check the yardage book — Review relevant codebase sections for files you'll modify
Scan for hazards — Check bunker_locations from recent scorecards and common issues

Post-Shot Routine (Per-Ticket, After Completion)

Score the shot — in_the_hole (perfect), green (landed), fairway (clean start), or miss direction
Record hazards — Note any gotchas encountered
Check for penalties — Tests break? Reverts needed?
Push — The last push is the recovery point

Read the full file on GitHub · 52 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 52 lines · 682 tokens per session scan A aa1d77bfa796

Subscribe to this mod's changes

slope-sprint-checklist is a cursor rule published in the GitHub repository srbryers/slope (6 stars, last pushed 3d ago), licensed MIT. It adds 682 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

slice-tasks

PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.

danielvm-git/bigpowers · 59 tokens

iris

GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.

ils15/pantheon-legacy · 43 tokens

elite-orchestrator

Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…

MN-Lizard-Team/aiyu-multi-agent · 94 tokens

slope-sprint-checklist