Sprint Planning and Review

Your agent pulls the backlog, proposes sprint scope against team capacity, summarises standups and reviews, and applies changes only after you approve a table of them.

Used by our operations team

What It Does

Runs a sprint from start to finish on top of the task tracker. At planning it proposes what goes into the sprint, based on priority and your capacity figures. Daily it writes a standup summary. At the end it counts what was committed, completed and carried over, and proposes how to close the sprint.

Before it changes the status, owner or due date of several tasks, it shows a table of every change and waits for your yes.

Who Uses It

Team leads and coordinators, at the start of a sprint, each morning for standups, and at sprint end.

Setup

1. Install and set up task-ops first. This skill requires it. Follow its backend/SETUP.md.
2. Copy the skill/ folder into your agent's skills folder as sprint-ops, for example .claude/skills/sprint-ops/. Or fetch it through the Thinqmesh MCP server.
3. In task-ops, edit references/team-config.md: your teams, sprint length and capacity per team. The default figures are an example only.
4. Make sure TASK_OPS_URL and TASK_OPS_KEY are set, as described in the task-ops setup.

Example Result

Proposed scope for S2026-04, Engineering (capacity 8-12)

ID   Title                 Field    Now      New
#31  Fix login timeout     status   Backlog  In Progress
#31  Fix login timeout     owner    -        sam@example.com
#31  Fix login timeout     due      -        2026-03-13
#34  Draft API changelog   status   Backlog  In Progress

2 tasks, 4 changes. Apply these?

How to Adapt

• Set sprint length and capacity per team in task-ops's references/team-config.md.
• Change the sprint naming format in this skill's SKILL.md.
• Change what counts as "at risk" in the standup section to match how your team works.