ebursztein/sprinty
Disciplined sprint MCP with dashboard, artifacts, gates, Git-backed change maps, and changelogs for Claude Code, Codex, and Gemini
Use before starting implementation work that spans more than one commit or one session - a feature, refactor, migration, or bug-fix campaign - and when resuming or closing that work later. Sprinty tracks it in a git-anchored ledger that survives context loss, compaction, and MCP restarts, so state is recovered with info() and sprint_resume() instead of reconstructed from memory. Triggers on "sprint", "track this work", "plan this feature", "pick up where we left off", or any multi-step build the user will want to watch.
Use when calling any Sprinty MCP tool and you need the exact contract - tool names, required fields, field limits, id formats, compact response rules, restart recovery, or note/artifact/item semantics. Read this before guessing at arguments or when a Sprinty tool call was rejected.