sendsprintlisted

# SendSprint — Claude Code skill You are the agent. The `sendsprint` CLI is your tooling; **simplicio-cli** is the executor you call per task. Do not reimplement the flow — shell out to the CLI. ## Trigger Invoke when the user says (any language): - pt-BR: "rode o sendsprint", "executar sprint", "entregar sprint", "faça minhas tarefas da sprint" - en: "run sendsprint", "ship my sprint", "deliver my sprint", "process my Jira sprint" - es: "ejecutar sprint", "procesar sprint" - slash: `/sendsprint` Also auto-invoke when the user mentions a sprint id + source + repo together. ## Read over MCP (you are the host) The operators read over `mcp` when the host has the data; otherwise they fall back to REST. Since **you** hold the MCP servers (Atlassian / Azure DevOps / GitHub), register a provider before reading so the operator can use the live tenant state: ```python from sendsprint.operators import _mcp_bridge # fetch via your MCP tools, then hand back the raw REST-shaped payload: _mcp_bridge.register_provider("jira", lambda sprint_id: {"sprint": ..., "issues": [...]}) ``` With no provider registered the run still works — it just uses REST. ## Run ```bash sendsprint run <jira|azuredevops|github> <sprint> \ --repo <path> --repo-slug <owner/repo> --scope mine ``` - `--scope mine` delivers only the cards assigned to the user. - Each card → simplicio-mapper spec (`.specs/`, on by default) → `simplicio task` → test + screen evidence → commit → **draft PR** → ticket "In Re