Skip to content
Development
Command

/session-report

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

From plugin
agent-skills-standard
57033 skills21 agents33 commands1 MCP
Install
$ npx -y skills add hoangnguyen0403/agent-skills-standard --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/session-report

Context preview

What this command does when you run it.

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

Command definition

session-report.md

Session Report

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

**Input:** $ARGUMENTS

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

Instructions

Execute the following steps for **$ARGUMENTS**.

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. Persist and route:

  • Write the run record to `artifacts/runs/[slug]/[compactISO]-session-report.json` when file writes are allowed.
  • 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
{schema_version: 1, run_id: "[run-id]", slug: "[slug]", workflow: session-report, feature_status: implemented, started_at: "[timestamp]", completed_at: "[timestamp]", requirement_trace: {brd_objectives: [], requirements: [], acceptance_criteria: [], srs: []}, completed_evidence: [], missing_evidence: [], decision_needed: [], recommended_next_workflow: retro-learn, cost: {source: unavailable}, agent: {identity: "[agent-identity]", model: "[model]"}}

## Next Workflow

## Cost Report
Call `get_session_cost(workflow="session-report")` before final handoff.
Read more
Ships withagent-skills-standard

The portable SDLC standards layer for AI coding agents. Sync once, then work in your own runtime.

Get the whole plugin

Other commands on agent-skills-standard.