gsd-session-report

Name: gsd-session-report
Availability: InStock
Author: Pear

Generate structured SESSION_REPORT.md files for GSD workflow runs.

Updated May 15, 2026

Search Tags:#token usage #work summary #workflow tracking #gsd workflow #session reporting #development documentation

Ready to run

npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-session-report-pear-commerce

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-session-report
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-session-report
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-session-report-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually compiling session work summaries, token usage estimates, and outcomes is time-consuming and inconsistent, making it difficult to share progress context with team members or archive workflow results for future reference.

Core Features & Use Cases

Structured Session Documentation: Automatically generates a standardized SESSION_REPORT.md file with all key session details.
Usage Tracking: Includes estimated token consumption and resource usage for the session.
Use Case: After completing a GSD workflow phase, use this skill to create a shareable report of all work performed, key decisions made, and outcomes achieved for team sync or project archival.

Quick Start

Use the gsd-session-report skill to generate a structured session report for the work completed in your current GSD workflow run.

Frequently Asked Questions about gsd-session-report

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

FAQPage Schema

How do I automatically generate a session report for development workflow runs?▼

To automatically generate a session report, use a skill that captures work outcomes, token usage estimates, and execution results to produce a standardized SESSION_REPORT.md file, eliminating manual documentation effort.

What is the best way to track token usage and work summaries for software development sessions?▼

Tracking token usage and work summaries is best handled by automating structured session documentation, which records estimated resource consumption and completed tasks into a shareable artifact for team synchronization.

How do I create shareable development documentation after completing a workflow phase?▼

Creating shareable development documentation involves generating a structured session report that captures key decisions, outcomes, and resource consumption, preserving context for future work and project archival.

Can I standardize post-session reporting to avoid manual work summary compilation?▼

Yes, you can standardize post-session reporting by automating the generation of structured artifacts that detail work outcomes and token usage estimates, replacing inconsistent manual reporting methods.

When do I need a structured session report for my GSD workflow?▼

You need a structured session report for your GSD workflow when teams require standardized, shareable artifacts to document session progress, resource consumption, and completed tasks for future reference.