gsd-session-report

Generate a SESSION_REPORT.md summarizing completed work and estimated token usage.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-session-report-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-session-report
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-session-report
Command: npx skills add https://github.com/coco-research/coco --skill gsd-session-report-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a completed work session into a clear SESSION_REPORT.md so you can review outcomes, capture what was done, and estimate resource usage without rebuilding the timeline manually.

Core Features & Use Cases

  • Session Summary: Captures the work performed, notable outcomes, and any remaining context.
  • Resource Estimation: Includes token usage estimates to help you understand session cost.
  • Shareable Artifact: Produces a structured report you can archive, hand off, or revisit later.
  • Use Case: After a debugging or implementation sprint, generate one concise report that explains the results and preserves the session context for others.

Quick Start

Ask the assistant to create a SESSION_REPORT.md for this session, including a concise summary of work completed, outcomes, and estimated token usage.

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 session report for a completed development sprint?

To generate a session report, prompt the assistant to create a SESSION_REPORT.md summarizing the work completed, notable outcomes, and estimated token usage. This structured artifact captures the session context for review and sharing.

What is the best way to document work performed and token usage for a developer handoff?

Documenting work performed and token usage for a handoff requires a structured session summary. The Skill generates a shareable report that captures outcomes, work performed, and resource consumption estimates to preserve session context for others.

Can I estimate token usage and resource consumption after a coding session?

Yes, you can estimate token usage and resource consumption after a coding session. The Skill evaluates the completed work and includes token usage estimates within the generated report to help you understand session cost.

Does generating a work summary require any specific dependencies or setup?

Generating a work summary requires no specific dependencies or setup. It operates directly on your completed developer-facing session to produce a structured markdown artifact summarizing outcomes and resource estimates.

When do I need a structured session review artifact?

You need a structured session review artifact when a concise record of outcomes and resource consumption is required. It is ideal for archiving, handing off, or revisiting the context of a debugging or implementation sprint later.