Session Report Skill
[!IMPORTANT]
Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, 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 inherited operator_profile from 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-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.
1---2name: session-report3description: Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.4---5# Session Report Skill67> [!IMPORTANT]8> Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.910Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.1112## Instructions1314When the user asks to perform this workflow, execute the following steps:151617# Session Report Workflow1819Goal: Preserve a concise artifact of what changed, how it was verified, and what should improve.2021## Steps22231. Collect session facts:24 - User goal, ticket/PR/spec links, changed files, commands run, test results, screenshots/logs, environments.25 - MCP/tool calls used when available; otherwise local command summaries and artifact paths.26 - Load `common-operator-profile`; carry the inherited `operator_profile` from the Handoff Payload without re-inferring it.272. Capture evidence:28 - Implementation summary tied to ACs or tasks.29 - Verification commands and PASS/FAIL/BLOCKED status.30 - Remaining risks, assumptions, and follow-up owners.313. Record requirements drift:32 - BRD-lite, PRD, and SRS/FRS updates completed or missing.33 - Traceability gaps found during implementation or verification.344. Route:35 - Remaining code work -> `implement-feature` or `dev-fix`.36 - Missing evidence -> `verify-work` or `traceability-audit`.37 - Standards update -> `retro-learn`.38 - Release communication -> `publish-notes`.3940## Runtime Contract41- Use at the end of a work session to preserve evidence and follow-ups before context is lost.42- Required inputs: session goal plus changed files or commands run during the session.43- Return BLOCKED only when no session evidence (changes, commands, or verification) exists to report.44## Handoff Payload45- `slug`, `operator_profile`, goal, changes, verification results, requirement-drift status, risks, follow-ups, next workflow.46## Blocking Questions47- Ask max 3 at a time with a recommended default and 2-3 options.4849## Output Template5051```md52# Session Report5354## Goal5556## Changes5758## Verification5960| Command/Check | Result | Evidence |61| --- | --- | --- |62| [check] | [result] | [evidence] |6364## BRD/PRD/SRS Update Status6566## Risks And Follow-Ups6768## Skill Feedback Candidates6970## Outcome Report71feature_status: partially_implemented | implemented | blocked72requirement_trace: BRD-OBJ-* -> REQ-* -> AC-* -> SRS-* -> evidence73completed_evidence: []; missing_evidence: []; decision_needed: []; recommended_next_workflow: implement-feature | verify-work | publish-notes | retro-learn7475## Next Workflow7677## Cost Report78Call `get_session_cost(workflow="session-report")` before final handoff.79```80