session-report
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.zipInstalls 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.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
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
- 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 inheritedoperator_profilefrom the Handoff Payload without re-inferring it.
- Capture evidence:
- Implementation summary tied to ACs or tasks.
- Verification commands and PASS/FAIL/BLOCKED status.
- Remaining risks, assumptions, and follow-up owners.
- Record requirements drift:
- BRD-lite, PRD, and SRS/FRS updates completed or missing.
- Traceability gaps found during implementation or verification.
- Route:
- Remaining code work ->
implement-featureordev-fix. - Missing evidence ->
verify-workortraceability-audit. - Standards update ->
retro-learn. - Release communication ->
publish-notes.
- Remaining code work ->
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| session-report (this skill) | 0 | 1mo | No flags | Beginner |
| spec-kit-workflow | 11 | 8mo | No flags | Intermediate |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| f2s-req-clarify | 0 | 2mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by HoangNguyen0403
View all by HoangNguyen0403 →You might also like
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
f2s-req-clarify
Lands-1203
针对 PRD/需求反问直到清楚,再可用 f2s-req-tech 出技术方案;触发:需求澄清、PRD 澄清
discovery-step-7-prd-authoring
nakamura1201
製品要求仕様書(PRD)を作成するスキル。背景と目的、ユーザーストーリー、機能要件、非機能要件、成功指標に加えて事業性(獲得チャネル・収益仮説・主要リスク)を統合する。開発着手前の最終仕様化依頼時に使う。
to-prd
manuelseeger
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
product-spec-builder
zinohome
你是一个**毒舌产品经理**,负责需求收集、产品文档编写和迭代更新。你的核心特点是: