vibe-sunsang-retro

Convert Codex JSONL conversation logs into structured Markdown retrospectives.

114|19|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/fivetaku/gptaku-plugins-codex --skill vibe-sunsang-retro-fivetaku
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-sunsang-retro
Source: https://github.com/fivetaku/gptaku-plugins-codex/tree/main/plugins/vibe-sunsang-codex/skills/vibe-sunsang-retro
Command: npx skills add https://github.com/fivetaku/gptaku-plugins-codex --skill vibe-sunsang-retro-fivetaku

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill converts raw Codex conversation logs into readable Markdown retrospectives, enabling teams to review past sessions and extract actionable insights.

Core Features & Use Cases

  • Conversation-to-Markdown conversion: transforms per-session dialogue into structured Markdown with context, goals, and friction points.
  • Retrospective framing: highlights main goals, recurring friction, collaboration moves, and verification moments.
  • Artifact export and indexing: exports retrospectives to a configurable output directory and generates an index for quick access.

Quick Start

Run the converter on your Codex session files to generate readable Markdown retrospectives in the designated output directory.

Frequently Asked Questions about vibe-sunsang-retro

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

FAQPage Schema
How do I convert Codex conversation logs into a readable Markdown retrospective?

To convert Codex conversation logs into a Markdown retrospective, you can use a tool that reads JSONL session data and assembles per-message context into a structured report. It automatically extracts goals, friction points, and verification moments.

What is the best way to export Codex session data for team review?

The best way to export Codex session data for team review is to generate structured Markdown summaries. This process transforms raw dialogue into concise retrospectives and exports them to a configurable output directory with an index for quick access.

Can I analyze multiple Codex workspaces and dates at once for a retrospective?

Yes, you can analyze multiple Codex workspaces and dates at once. The conversion process applies to recent sessions across different workspaces and dates, producing a consolidated Markdown retrospective of goals and collaboration moves.

Does converting JSONL session data into Markdown require any external dependencies?

Converting JSONL session data into Markdown does not require external dependencies. The conversion is handled entirely by internal scripts that read the raw Codex logs and structure them into a readable retrospective format.

What specific insights are highlighted when generating a retrospective from Codex logs?

Generating a retrospective from Codex logs highlights main goals, recurring friction, collaboration moves, and verification moments. This structured Markdown framing enables teams to review past sessions and extract actionable insights.

Are there limitations when transforming per-session dialogue into structured Markdown?

A limitation of transforming per-session dialogue into structured Markdown is that the output quality depends on the JSONL session data provided. The tool focuses on recent sessions, so older logs may require manual filtering before conversion.