team-ops

Prime a session with a team project's current state - backlog, sprint, repo progress - and refresh its _index.md summary. Use when the user asks "where are we" on a team project, or at the start of a work session on one.

Add, refine, split, or reorder PBIs in the file-based product backlog in the team-shared folder. Use when the user wants to create backlog items, write user stories or acceptance criteria, estimate points, split oversized items, or tidy the product backlog.

Plan a sprint - set the goal, commit backlog items into scope, and write the burndown baseline (scope.json). Use at a sprint boundary when the user wants to plan the next sprint or commit items to a sprint.

Generate the daily progress report - PBI status board, burndown chart, and merges of the day - as a self-contained HTML file in the team-shared folder. Use in the daily routine, or when the user asks for today's progress report or a burndown chart.

Write the sprint review - scope vs done, demo pointers, and carry-over decisions. Use at sprint end when the user wants a sprint review, sprint summary, or to close out a sprint.

Set up team-ops for this machine/project - create .claude/team-context.json, scaffold the team-shared ai/ folder skeleton, and optionally register a project. Use when onboarding a machine to a team shared folder, when the team-context hook reports a config error, or when adding a new team project.

Start work on a PBI - set it to doing and issue the convention-compliant work branch name (pbi/<id>-<slug>). Use when a developer picks up a backlog item, or asks which branch name to use for a PBI.

Rebuild or repair the team knowledge base indexes (_index.md files) in the team-shared folder. Use after several notes were added or moved, when indexes look stale, or when team-kb-save reports a larger reshuffle is needed.

Answer questions from the team-shared knowledge base. Use when the user asks about team rules, working agreements, domain knowledge, past decisions, or anything a teammate might have documented in the shared folder.

Save reusable team knowledge into the team-shared knowledge base. Use when this session surfaces a process gotcha, decision rationale, domain know-how, or team rule worth sharing with teammates, or when the user asks to save something to the team KB.

Generate an onboarding briefing for a new team member from the team KB, project specs, and recent progress. Use when someone new joins the team or a project, or when the user asks for an onboarding guide / "explain this team to a newcomer".

Update the project's living spec (docs/spec/spec.md) from PBI acceptance criteria and diffs newly merged into the dev-main branches. Use in the daily routine after repo sync, or when the user asks to bring the spec up to date with what is implemented.

Facilitate and record a sprint retrospective (KPT) with follow-up on the previous retro's action items. Use at sprint end when the user wants a retrospective, KPT, or team improvement discussion.