sprint-checkin
Executes sprint check-in procedures to align goals, track blockers, and manage project artifacts.
Install
mkdir -p .claude/skills/sprint-checkin && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17914" && unzip -o skill.zip -d .claude/skills/sprint-checkin && rm skill.zipInstalls to .claude/skills/sprint-checkin
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Start of sprint: carry-over, goals, blockers, sprint plan artifact; get_slash_command: sprint-checkinKey capabilities
- →Load the canonical sprint playbook
- →Coordinate with Tracker, GitHub, and shell tools
- →Guide developers through check-in routines
- →Ensure all team requirements are met during the start of a sprint
How it works
The skill loads a canonical sprint playbook from the Coherence Engine MCP server to provide step-by-step guidance for sprint check-in activities.
Inputs & outputs
When to use sprint-checkin
- →Sync sprint goals and artifacts
- →Identify and document sprint blockers
- →Manage carry-over work between sprints
- →Initialize sprint planning sessions
About this skill
CE: sprint-checkin
Load the playbook (MCP)
- Ensure the Coherence Engine MCP server is connected in your AI tool (see https://coherence-engine.fly.dev/docs/ for connection details).
- Load the canonical playbook text:
- Call
resources/readwith URIce://commands/sprint-checkin(pluralcommands), or - Call
get_slash_commandwithcommand_name:sprint-checkin
- Call
- Follow the loaded playbook step by step. Use Tracker, GitHub, shell, and other tools exactly as the playbook specifies.
If the resource read fails
- Confirm the MCP server URL and auth.
- Retry with
get_slash_commandandsprint-checkin. - Do not assume a local copy of this playbook in the project - init does not copy playbook bodies; those files live on the MCP server and in the framework repo for authoring only.
All commands
All commands load via get_slash_command with the kebab-case name or from ce://commands/{name} (see https://coherence-engine.fly.dev/ce/docs/commands.md).
When not to use it
- →If the Coherence Engine MCP server is not connected
- →If the resource read fails and cannot be resolved
- →When assuming a local copy of the playbook in the project
Limitations
- →The MCP server URL and auth must be confirmed if resource read fails
- →Playbook bodies live on the MCP server and in the framework repo for authoring only
- →All commands load via `get_slash_command` or from `ce://commands/{name}`
How it compares
This skill centralizes sprint check-in guidance through a managed playbook, ensuring consistency across teams and tools, unlike ad-hoc check-in processes.
Compared to similar skills
sprint-checkin side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sprint-checkin (this skill) | 0 | 1mo | No flags | Beginner |
| workflow-router | 1 | 6mo | Review | Intermediate |
| loki-mode | 1 | 6mo | Review | Advanced |
| wg | 0 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
workflow-router
parcadei
Goal-based workflow orchestration - routes tasks to specialist agents based on user goals
loki-mode
davila7
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention. Features Task tool for subagent dispatch, parallel code review with 3 specialized reviewers, severity-based issue triage, distributed task queue with dead letter handling, automatic deployment to cloud providers, A/B testing, customer feedback loops, incident response, circuit breakers, and self-healing. Handles rate limits via distributed state checkpoints and auto-resume with exponential backoff. Requires --dangerously-skip-permissions flag.
wg
graphwork
Use this skill for task coordination with WG. Triggers include "wg", task graphs, multi-step projects, tracking dependencies, coordinating agents, or when you see a .wg directory.
run-tasks
JeremyKalmus
Orchestrate task execution via beads and sub-agents. Gets ready work from beads, spawns appropriate agents based on labels, monitors completion, and updates status. Use after /approve-spec has created tasks.
start-dev-team
trysmr
>
rudhra-swarm
Abhishek21g
Orchestrate multiple specialized agents or agent roles for a project. Use when the user says "rudhra swarm", "spin multiple agents", "orchestrate agents", "parallel agents", "agent team", "multi-agent review", or asks Rudhra to split work across mapper, researcher, implementer, tester, reviewer, and