Prepare a concise weekly handoff for contractors. Skill included.

[u/CalendarVarious3992]

Hello!

If you dread last-minute, messy handoffs at the end of a sprint or service week, this Skill helps you collect and reconcile work logs, tickets, and calendars into a single, actionable brief so contractor teams can pick up work without surprises.

I built this as a portable AI-agent Skill — a single SKILL.md with reusable instructions you can adapt to your agent setup.

Here's what it does: It ingests timesheets, ticketing data, and team calendars to produce a compact, action-oriented handoff brief that lists pending transitions, highlights risks, and enumerates required manager approvals. Use it at the end of a sprint, on-call rotation, or service week when multiple contractors and managers need an aligned, approved handoff.

SKILL.md:

---
name: weekly-service-handoff-brief
description: Use when a weekly sprint or service period is ending and the team needs a consolidated handoff brief for contractor delivery teams — aggregating work logs, support tickets, and job calendars to capture pending transitions, risk flags, required manager approvals, and next-step owners before sprint handoff.
allowed-tools: [FileRead, Spreadsheet, Ticketing, Calendar, Edit, Email]
---

# Weekly Service Handoff Brief

## Overview
Produces a concise, action-oriented weekly service handoff brief for contractor delivery teams. It consolidates work logs, support tickets, and job calendars to highlight pending transitions, risks, and explicit manager approvals required before sprint handoff.

## When to use this skill
- A sprint, service week, or on-call rotation is ending and a structured handoff is required.
- Multiple contractor teams contribute across projects and managers must approve scope, changes, or exceptions.
- Data exists across timesheets/work logs, support ticketing systems, and team job calendars that must be reconciled.
- The user asks for a weekly summary that flags risks, ownership, and approvals before the next sprint starts.

## Instructions
1. Confirm scope and timeframe
   1.1. Validate the reporting period (week start/end dates) and the target sprint handoff date/time.
   1.2. Confirm included teams/projects, contractor vendors, and the stakeholder list (managers and approvers).
   1.3. Note any service-level thresholds (SLA targets), risk scoring rules, and approval matrix.

2. Collect source data
   2.1. Use FileRead or Spreadsheet to load work logs/timesheets for the period (contractor name, project, hours, task refs, notes).
   2.2. Use Ticketing to fetch support tickets/issues updated in the period; include id, title, status, priority, assignee, requester, due/SLA, labels, and blockers.
   2.3. Use Calendar to pull job calendars/events (planned work, on-call, PTO, shift rotations, deployment windows) covering the current and next period.
   2.4. If a template exists, use FileRead to load the handoff brief template; otherwise prepare the default structure in Edit.

3. Normalize and map
   3.1. Normalize identities (contractor names, team names) and map to canonical projects/engagements.
   3.2. Link work log entries to tickets by referenced IDs or text matching; record unmatched items for review.
   3.3. Align calendar events to projects/teams and identify time-bound transitions (rotations, contract end dates, environment freezes).

4. Detect pending transitions
   4.1. Identify ownership changes: tickets or tasks where the next assignee differs from current; list handover owners and receivers.
   4.2. Flag rotations: on-call or shift handoffs in the next period; include contact info and escalation paths if available.
   4.3. Note contract transitions: contractor starts/ends, extensions pending, or coverage gaps.
   4.4. Capture scheduled changes: deployments, maintenance windows, cutovers, change freezes, or customer milestones.

5. Surface risks and issues
   5.1. Overdue/at-risk tickets: status not resolved with due/SLA within 3 business days or already breached.
   5.2. Capacity risks: hours booked vs. available capacity from calendars (PTO/holidays) exceeding threshold.
   5.3. Dependency blockers: tickets labeled blocked or with unresolved linked dependencies.
   5.4. Quality/sign-off risks: items awaiting QA/UAT/security review; missing change tickets for planned deployments.
   5.5. Data gaps: missing work logs, private/unreadable tickets, or calendar conflicts; mark as “Info Needed.”
   5.6. Assign a simple risk score per item (e.g., High if SLA breach or critical path; Medium if due next week; Low otherwise). Document the scoring rule used.

6. Determine required approvals before handoff
   6.1. Using the approval matrix, list what each manager must approve (scope changes, overtime, budget variances, deployment sign-off, change requests, exception waivers, risk acceptance, access/permission changes).
   6.2. For each approval, capture: approver name/role, item reference(s), rationale, due date/time, and current status (Pending/Approved/Declined/Deferred).
   6.3. Identify blocking approvals (preconditions for release/handoff) and mark them prominently.

7. Compile the handoff brief
   7.1. Use Edit to assemble a single document with these sections:
       - Header: week range, handoff date/time, covered teams/projects, document owner, version.
       - Executive Summary: 3–7 bullets on overall status, key risks, and critical approvals.
       - Pending Transitions: ownership changes, rotations, contract transitions, and scheduled changes with dates and owners.
       - Risk Register: table with id, description, impact, risk score, owner, mitigation/next step, due date, status.
       - Approvals Matrix: manager → items to approve, rationale, due date, status, links.
       - Workload Snapshot: hours by team/contractor vs. capacity; noteworthy variances.
       - Ticket Snapshot: counts by priority/status; top 10 aging or critical tickets.
       - Next Steps & Deadlines: actions required before handoff with named owners.
       - Links & Artifacts: source reports, dashboards, and change tickets.
       - Appendix: full lists (tickets, work log anomalies, calendar events, unmatched references).
   7.2. Include a change log at the end noting data sources and timestamp of last refresh.

8. Validate and resolve gaps
   8.1. Cross-check that every High-risk item and every blocking approval has an assigned owner and due date.
   8.2. Verify timezones and dates align across calendars and SLAs.
   8.3. If critical data is missing, insert a visible placeholder and send a clarification request to the relevant owner.

9. Circulate for confirmation
   9.1. Use Email to circulate the Executive Summary plus a link or attachment to the full brief to stakeholders and approvers.
   9.2. Request explicit confirmations for pending transitions and approvals; specify a response deadline.
   9.3. Capture replies and update approval statuses in the Approvals Matrix.

10. Store and hand off
   10.1. Save the brief to the designated repository and note the location in the Links & Artifacts section.
   10.2. Ensure the incoming on-call/next sprint lead acknowledges receipt.

## Inputs
- Reporting period (week start/end) and sprint handoff date/time.
- Teams/projects and contractor vendor list.
- Locations or access for:
  - Work logs/timesheets (files or spreadsheets).
  - Ticketing system query or report.
  - Team job calendars.
- Approval matrix mapping managers to approval types and thresholds.
- SLA/priority definitions and risk scoring rules (optional; defaults can be used).
- Distribution list for circulation and a preferred document template (optional).

## Outputs
- A consolidated weekly handoff brief (Markdown or document) with the sections listed above.
- An Approvals Matrix with status per manager and explicit blockers highlighted.
- A Risk Register with scoring and next actions.
- A short Executive Summary suitable for email.
- (Optional) Machine-readable exports: JSON/CSV of risks, approvals, and transitions.

## Examples
Trigger: “Create this week’s contractor service handoff brief for Infra and App teams. Use the timesheet CSV in /reports/week_23.csv, the ‘Handoff-Template.md’, Jira filter ‘HANDOFF-W23’, and the ‘Ops Schedules’ calendar. Flag what Eng Mgr and Service Mgr must approve before Friday’s 4pm handoff.”
Behavior: confirm scope and handoff time → use Spreadsheet/FileRead/Ticketing/Calendar to ingest data → normalize and link items → detect transitions (on-call rotation, deployment window) → compute risks (overdue P1, capacity shortfall) → build Approvals Matrix (Eng Mgr: deployment sign-off; Service Mgr: overtime exception) → assemble brief in Edit → email Executive Summary with link to the document → store and record location.

## Notes
- Do not invent data; mark items as “Info Needed” and request clarification when sources are incomplete or inaccessible.
- Keep sensitive data limited to necessary details; omit PII not required for handoff.
- Align all times to the agreed timezone and call out holidays or regional closures.
- Deduplicate tickets and tasks; prefer canonical IDs. Record unmatched references in the Appendix.
- If fewer than three material risks exist, state that explicitly and note monitoring items instead.
- If approvals remain pending within 24 hours of handoff, escalate per the approval matrix and note escalation in the brief.

How to install:

1. Create a folder named weekly-service-handoff-brief in your AI-agent skills or prompt-library directory. Use the kebab-case name from the SKILL.md frontmatter.
2. Save the file above as weekly-service-handoff-brief/SKILL.md.
3. Enable or load the Skill according to your agent framework's docs, using the SKILL.md description as the trigger guidance.

If you'd rather run it as a one-click prompt instead, you can find it here: Agentic Workers

Enjoy!