Records a summary of development session progress, verification, and improvements.

Install

mkdir -p .claude/skills/session-report && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12497" && unzip -o skill.zip -d .claude/skills/session-report && rm skill.zip

Installs to .claude/skills/session-report

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.
106 charsno explicit “when” trigger
Beginner

Key capabilities

  • Collect session facts
  • Capture evidence of implementation and verification
  • Record requirements drift
  • Route to next workflow based on status
  • Generate a structured session report

How it works

This skill collects information about a work session, including changes, commands, and verification results, to generate a structured report.

Inputs & outputs

You give it
Session goal, changed files, or commands run during the session
You get back
A markdown session report detailing changes, verification, risks, and next steps

When to use session-report

  • Document progress
  • Create session report
  • Handoff work

About this skill

Session Report Skill

[!IMPORTANT] Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

Session Report Workflow

Goal: Preserve a concise artifact of what changed, how it was verified, and what should improve.

Steps

  1. Collect session facts:
    • User goal, ticket/PR/spec links, changed files, commands run, test results, screenshots/logs, environments.
    • MCP/tool calls used when available; otherwise local command summaries and artifact paths.
    • Load common-operator-profile; carry the inherited operator_profile from the Handoff Payload without re-inferring it.
  2. Capture evidence:
    • Implementation summary tied to ACs or tasks.
    • Verification commands and PASS/FAIL/BLOCKED status.
    • Remaining risks, assumptions, and follow-up owners.
  3. Record requirements drift:
    • BRD-lite, PRD, and SRS/FRS updates completed or missing.
    • Traceability gaps found during implementation or verification.
  4. Route:
    • Remaining code work -> implement-feature or dev-fix.
    • Missing evidence -> verify-work or traceability-audit.
    • Standards update -> retro-learn.
    • Release communication -> publish-notes.

Runtime Contract

  • Use at the end of a work session to preserve evidence and follow-ups before context is lost.
  • Required inputs: session goal plus changed files or commands run during the session.
  • Return BLOCKED only when no session evidence (changes, commands, or verification) exists to report.

Handoff Payload

  • slug, operator_profile, goal, changes, verification results, requirement-drift status, risks, follow-ups, next workflow.

Blocking Questions

  • Ask max 3 at a time with a recommended default and 2-3 options.

Output Template

# Session Report

## Goal

## Changes

## Verification

| Command/Check | Result | Evidence |
| --- | --- | --- |
| [check] | [result] | [evidence] |

## BRD/PRD/SRS Update Status

## Risks And Follow-Ups

## Skill Feedback Candidates

## Outcome Report
feature_status: partially_implemented | implemented | blocked
requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence
completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: implement-feature | verify-work | publish-notes | retro-learn

## Next Workflow

## Cost Report
Call `get_session_cost(workflow="session-report")` before final handoff.

When not to use it

  • When no session evidence exists to report
  • When the goal is not to preserve evidence and follow-ups

Limitations

  • Requires session goal plus changed files or commands run
  • Returns BLOCKED if no session evidence exists
  • Relies on `get_session_cost` for cost reporting

How it compares

This workflow provides a standardized template and process for documenting work sessions, unlike ad-hoc note-taking.

Compared to similar skills

session-report side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
session-report (this skill)01moNo flagsBeginner
spec-kit-workflow118moNo flagsIntermediate
product-manager-toolkit327moReviewBeginner
f2s-req-clarify02moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry