Engineering Session Status & Handoff Report
Turn session changes, test results, and open decisions into an evidence-backed team update with clear handoff steps.
Before & after
Same prompt, same agent — the only difference is the skill.
I'd be happy to help you create a status report for your sprint. To make it most effective for your team meeting, I should know a few things: What were your main goals for this sprint? Which items did you complete versus which are still in progress? Were there any blockers or challenges your team faced? Also, it would help to know your team size and whether you want to include metrics like velocity or burndown. Once you share these details, I can draft a comprehensive report that covers all the key points your team needs to hear.
SPRINT STATUS REPORT - Week Ending July 31 COMPLETED ITEMS (8 total) • User auth refactor: Full migration to token-based sessions • Dashboard redesign: New responsive layout deployed to staging • API rate limiting: Implemented per-user quotas with sliding window • Documentation: Updated 12 endpoint refs for v2 migration IN PROGRESS (5 total) • Payment webhook retry logic: 80% complete, code review pending • Mobile app sync: Build optimization in testing • Database migration prep: Schema diff generated, approval needed BLOCKERS (2) -> Payment processor: Delayed API cert update, blocking webhook tests (Unblocked Wed) -> DevOps capacity: One engineer OOO, may slip mobile build by 1 day NEXT WEEK FORECAST • 6 items queued (3 high priority) • Estimated completion: 5 items, contingent on blocker resolution • Team capacity: Full (engineer returns Monday)
About this skill
“What actually got done, did the checks pass, and where should I pick this up?” A commit list rarely answers all three. This skill turns a work session into a concise team update that separates implemented changes, observed verification, unfinished work, and decisions needed.
What it does
- Groups file changes, commands, and decisions by outcome instead of replaying the session chronologically.
- Reconciles failed attempts, later fixes, reverted edits, and interrupted commands so the report reflects the final known state.
- Separates implementation status from test results, review readiness, merge state, and deployment evidence.
- Makes blockers actionable with their impact, the decision or input needed, and the next step.
- Builds a handoff around the current workspace state, remaining acceptance criteria, and the first useful action.
- Adjusts the report for a short team message, stakeholder update, or detailed engineering handoff.
What you get
A ready-to-share session report with checkable completion claims, scoped verification results, explicit unknowns, and ordered next steps. File locations, commands, and ownership appear only when supported by the available record.
Best for
Developers wrapping up a coding session, technical leads reviewing agent work, and engineers handing unfinished changes to another teammate.
SKILL.md preview
---
name: engineering-session-status-handoff-report
description: Compile engineering session changes, command results, and decisions into an evidence-backed status report and actionable handoff. Reconcile the final known state, separate implementation from verification, and identify unfinished acceptance criteria. Use when the user says "report what we did", "wrap up this session", "write a team update", "hand this off", "what is actually done?", "the summary says done but tests are failing", or "turn these logs into a status report".
---
# Engineering Session Status & Handoff Report
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.