SKILL

Handoff

Compact the current conversation into a handoff document for another agent to pick up. References existing artifacts (PRDs, plans, ADRs, issues, commits, diffs) by path or URL instead of duplicating them. Use when user wants to hand off the conversation to a fresh agent or starts a new session that picks up prior work.

Published by @Alireza Rezvani·0 agent reads / 30d·0 saves·

Handoff

Derived from Matt Pocock's handoff (MIT). Matt's no-duplication discipline preserved verbatim. Additions: tools + references + cs-* wrapper (see references/companion_tooling.md).

Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to a path produced by mktemp -t handoff-XXXXXX.md (read the file before you write to it).

Suggest the skills to be used, if any, by the next session.

Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.

If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.

Sections

  • Goal of next session (from user argument or inferred)
  • State of play (what's done, what's blocking)
  • Open decisions (what the next agent must decide)
  • Skills to use (concrete list)
  • Artifacts (paths/URLs to PRDs, plans, ADRs, issues, branches, PRs — do not duplicate)

Tooling

See references/companion_tooling.md. Tools: template + dedup + recommender. Agent: cs-handoff-author. Command: /cs:handoff.

Version: 1.0.0 Derived: Matt Pocock (MIT) + this repo's wrapper

Bundled with this artifact

8 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL▲0

Sprint Velocity Analysis

Analyze sprint velocity data and produce an engineering team health report covering delivery trends, capacity utilization, and improvement recommendations. Use when asked to analyze sprint velocity, review team delivery health, identify delivery risks, or produce a retrospective data analysis. Produces a velocity trend analysis, health diagnosis table, top improvement recommendations with implementation steps, and a next-sprint capacity forecast.

Mohit Aggarwal
software-engineering+2
⊙ 0
SKILL▲0

Runbook Writer

Write an operational runbook for a service, incident type, or deployment procedure. Use when asked to write a runbook, create an ops guide, document an operational procedure, or prepare an incident response playbook. Produces a runbook with overview, prerequisites, step-by-step procedures, rollback steps, troubleshooting table, and escalation paths.

Mohit Aggarwal
software-engineering+2
⊙ 0
SKILL▲0

Scrum Master

Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.

Alireza Rezvani
project-management+2
⊙ 0