gsd-session-report

To generate a session report, execute the reporting skill to automatically produce a structured SESSION_REPORT.md file. This document captures work summaries, project outcomes, and estimated token usage, providing a professional artifact for post-session review and stakeholder documentation.

Tracking token usage and work summaries is handled automatically by generating a structured session report document. It estimates resource consumption and summarizes the work performed, ensuring consistent project reporting and transparency without requiring manual calculations or logging.

Yes, generating session summaries requires access to the session-report workflow script to execute the reporting process end-to-end. This script enables the skill to extract session data, estimate token usage, and compile the final structured markdown documentation.

Yes, you can use automated reporting to instantly generate a professional summary artifact for stakeholders. The process creates a structured SESSION_REPORT.md file that captures key session details, outcomes, and resource tracking, ensuring consistent project documentation.

A key limitation is the dependency on the session-report workflow script; without access to it, the reporting process cannot execute end-to-end. Additionally, the skill provides estimated token usage rather than exact metrics, which may affect precise resource tracking.

You need to create a structured session report file after completing a complex coding or research session. It facilitates post-session review by summarizing work performed, documenting outcomes, and estimating token usage for personal review or stakeholder transparency.