skills.rest
pavelvdo
pavelvdoCOMMUNITY
Explore all skills by this author →
GitHub

kit-session-retro

Writes a dated session retrospective markdown file with worked, improve, and backlog sections.

Updated Jun 26, 2026
Search Tags:#feedback#documentation#markdown#retrospective#session#cursor#1c
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill kit-session-retro-pavelvdo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kit-session-retro
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/session-retro
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill kit-session-retro-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams lose informal feedback about what worked and what did not during a development session. This Skill captures a short retrospective in a dated markdown file so lessons learned are preserved without touching code or change requests. ## Core Features & Use Cases - Dated Retro File: Creates temp/session-retro-YYYY-MM-DD.md with sections for what worked, what to improve, and optional backlog ideas. - No Side Effects: Explicitly avoids running apply/writer steps or modifying code, keeping the retrospective purely documentary. - Use Case: After a long 1C development session in Cursor, invoke /session-retro to record friction points and improvement ideas, then optionally turn them into a new change request via /opsx:explore. ## Quick Start Ask the assistant to run /session-retro to record a short retrospective of the current session into a dated markdown file.

Frequently Asked Questions about kit-session-retro

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

FAQPage Schema
How do I record a session retrospective in the kit-van Cursor workflow?▼

Invoke the /session-retro command in the chat. The assistant creates a file named temp/session-retro-YYYY-MM-DD.md with sections for what worked, what to improve, and optional backlog ideas, then reports the file path.

What file does the session retrospective create and where?▼

It creates a markdown file at temp/session-retro-YYYY-MM-DD.md using the local date. The file contains three sections: what worked, what to improve, and optional backlog ideas for the kit.

Does the retrospective skill modify code or run apply steps?▼

No. The skill explicitly forbids running apply or writer steps and does not modify any code. It only writes the retrospective markdown file and reports its path in the chat.

Can retrospective ideas become change requests automatically?▼

No. Backlog ideas are recorded as optional notes only and no change request (ZNИ) is created automatically. To start one, the user must separately run /opsx:explore.

When should I use session-retro instead of a full change request?▼

Use it when you want to capture lightweight feedback about the session itself rather than a product defect or feature. It is a documentation-only step with no code changes, unlike the full explore-new-verify-apply cycle.

Related Skills

Explore More Software Engineering Skills→
Duy-Nguyen-2006Duy-Nguyen-2006

ck:journal

Creates concise journal entries documenting recent changes and session reflections.

Community
Basic
thompson0012thompson0012
28

generator-brainstorm

Transform vague backlog ideas into structured exploration artifacts in docs/live/ideas.md.

Community
Intermediate
cheng80cheng80
1

context-save

Capture git state, decisions, and remaining work for session resumption.

Community
Advanced
qa-amanqa-aman
11

mom

Convert raw meeting notes or transcripts into Smart Brevity minutes of meeting files.

Community
Intermediate