workflow-retrospective

Conduct structured session retrospectives to identify tooling friction and propose improvements.

Updated Mar 20, 2026

Search Tags:#workflow #tooling #retrospective #reflection #process #opencode #continuous-improvement

Ready to run

npx skills add https://github.com/developer239/marek-opencode --skill workflow-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-retrospective
Source: https://github.com/developer239/marek-opencode/tree/main/src/skills/workflow-retrospective
Command: npx skills add https://github.com/developer239/marek-opencode --skill workflow-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retrospective workflow solves the challenge of identifying tooling friction and proposing self-healing improvements after a session, turning vague reflections into concrete actions.

Core Features & Use Cases

Structured reflection prompts that capture tool friction, user clarifications, decisions, and bottlenecks.
Step-by-step guidance through the six-stage process: reflection, investigation, proposal, approval, implementation, and reporting.
Output a prioritized improvement plan with owner assignments and timelines for the next development cycle.

Quick Start

Review the current session using this workflow to identify friction points and propose actionable tooling improvements.

Frequently Asked Questions about workflow-retrospective

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

FAQPage Schema

How do I identify tooling friction after a development session?▼

You can identify tooling friction by conducting a structured post-session retrospective that reflects on conversation history, user clarifications, and workflow gaps to pinpoint specific bottlenecks.

What is the best way to turn vague process reflections into actionable improvements?▼

The best way to turn vague reflections into actionable improvements is using a guided workflow that processes session history through reflection, investigation, proposal, approval, implementation, and reporting stages.

How do I generate a prioritized improvement plan from workflow bottlenecks?▼

Generate a prioritized improvement plan by applying a retrospective workflow that evaluates continuous-improvement opportunities and outputs actionable changes with owner assignments and timelines for the next development cycle.

Can I use a retrospective workflow for continuous process improvement in software engineering?▼

Yes, a retrospective workflow supports continuous process improvement by providing structured reflection prompts and self-healing guardrails to systematically capture decisions and propose tooling changes.

Does the retrospective process require any external dependencies or components?▼

No, the retrospective process requires no external dependencies or components, operating entirely within the active session to analyze conversation history and generate workflow improvement reports.

When should I not use a structured session retrospective?▼

You should avoid a structured session retrospective if your active session lacks sufficient conversation history or workflow gaps to analyze, as the process relies on reflecting on prior interactions to propose improvements.