Process Retrospective

Community

Owl-Listener

process-retrospective

Audit and improve an existing process.

Overview

Publisher	Owl-Listener
Repository	`ux-pgm-skills`
Skill name	`process-retrospective`
Stars	4
Forks	0
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by Owl-Listener on GitHub. Read the source before you install it.

Installation

Install the Process Retrospective AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Owl-Listener/ux-pgm-skills/tree/main/process-design/skills/process-retrospective
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Owl-Listener/ux-pgm-skills/tree/main/process-design/skills/process-retrospective

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Owl-Listener/ux-pgm-skills.git /tmp/ux-pgm-skills
mkdir -p .claude/skills
cp -r /tmp/ux-pgm-skills/process-design/skills/process-retrospective .claude/skills/process-retrospective

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Process Retrospective in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Process Retrospective on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Process Retrospective is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Process Retrospective

You are an expert at finding and fixing the friction in how work gets done.

What You Do

You diagnose where a process is failing and recommend targeted, owned improvements.

Method

Map the process as it really runs, not as documented
Gather data: cycle time, rework, complaints, drop-off points
Find the few constraints causing most of the pain
Ask why each exists before removing it (some friction is load-bearing)
Propose a small set of changes, each owned and measurable
Re-measure after, to confirm the fix worked

Diagnostics

Where does work wait the longest?
Where is work most often redone?
Which step do people quietly route around?

Best Practices

Fix the constraint, not the symptom near it
Change one or two things, then measure — not everything at once
Some friction protects quality; don't strip it blindly

Frequently asked questions

What does the Process Retrospective AI skill do?

Audit and improve an existing process.

Why use Process Retrospective on TypingMind?

Because you install it once and use it with any model. Process Retrospective is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Process Retrospective in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Owl-Listener/ux-pgm-skills/tree/main/process-design/skills/process-retrospective. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Process Retrospective?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Process Retrospective?

As many as you like. As long as a model supports skills, you can use Process Retrospective with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Process Retrospective AI skill free?

Yes. It is published on GitHub by Owl-Listener under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Stats

JuliusBrussee

CommunityPopular

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Openclaw Test Heap Leaks

openclaw

OrganizationPopular

Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Process Retrospective

What You Do

Method

Diagnostics

Best Practices

Frequently asked questions

Related AI Skills

Set up your own AI workspace now