gsd-session-report

Generate a structured SESSION_REPORT.md with token usage estimates, work performed, and outcomes.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-session-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-session-report
Source: https://github.com/onelee85/my-skills/tree/main/gsd-session-report
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-session-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate a structured session report capturing token usage estimates, work performed, and outcomes.

Core Features & Use Cases

  • Generate a SESSION_REPORT.md with token usage estimates, work performed, and outcomes for post-session reviews.
  • Execute the deterministic session-report workflow end-to-end to ensure consistent results across runs.
  • Produce a shareable artifact suitable for stakeholders and team retrospectives.

Quick Start

Invoke the gsd-session-report skill with your recent session notes to generate a SESSION_REPORT.md.

Frequently Asked Questions about gsd-session-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a post-session report for a sprint retrospective?

A session report is a structured markdown document capturing token usage estimates, work performed, and outcomes. It is needed for post-session debriefs, after-action reviews, or sprint retrospectives to summarize activities and results.

Can I get consistent work-summary results across multiple report generations?

Token usage estimates are calculated automatically during the report generation process. The skill captures these metrics alongside the work performed and outcomes, including them directly in the generated SESSION_REPORT.md file.

What is the best way to create a shareable session report from workflow activities?

To generate a session report, invoke the skill with your recent session notes. It executes a deterministic workflow to automatically produce a structured SESSION_REPORT.md capturing work performed and outcomes for review.

Does this session-report workflow require any external dependencies to run?

Yes, the generated SESSION_REPORT.md is a shareable artifact suitable for stakeholders. It structures work summaries, decisions, and token usage estimates into a clear document for team retrospectives.