using-sprinty
Installation
SKILL.md
Using Sprinty
Prefer compact commands first. Lists are compact and say which _get() tool returns full detail. Mutating tools return acknowledgements plus next_tools, concrete follow-up calls derived from live state; do not expect or request full sprint dumps from mutations.
Core Tools
| Tool | Input | Use |
|---|---|---|
info |
{ git_dir?, data_dir?, workspace_dirs?[] } |
First-call orientation before binding. Returns startup workflow, resume/create help, dashboard state, and sprint rows with title, created time, and open/closed/blocked item counts. |
sprint_resume |
{ git_dir, data_dir?, agent_token? } |
Rebind this MCP process to an existing sprint. Returns a bounded briefing (counts, current item, blocked ids, last resolved, recent notes), the skills to read, and the dashboard URL - use it instead of re-deriving state with overview+next. data_dir defaults to <git_dir>/.sprinty. Never call sprint_new as a resume trick. |
sprint_detach |
{} |
Clear this process binding before resuming a different sprint; only the sole attached agent may detach the connection. |
sprint_new |
{ goal, git_dir, data_dir?, context_notes?[], agent_token? } |
Start one sprint with explicit git_dir; data_dir defaults to <git_dir>/.sprinty. Returns the dashboard URL. |
overview |
{} |
Compact sprint title/details/artifacts/subsprints/items. Use this to orient. |
next |
{ past?=1, future?, future_per_subsprint?=1, include_high_priority?=true } |
Compact active work window. Prioritizes your claims, then unclaimed ready work; applies high-priority and per-subsprint window settings. Suggested work still needs an atomic claim. future caps the total returned across all subsprints. No full graph. |
search |
{ pattern, context_size?=512 } |
Regex search. Returns { id, type, text, tool_call }; use tool_call for full detail. |
dashboard_info |
{} |
Current localhost dashboard URL and port, or running:false when stopped. |
dashboard_restart |
{} |
Restart the dashboard server and return the new URL and port. |