qrspi-retrospective

Capture QRSPI retrospective friction and propose prompt and process edits.

2|Updated Jun 6, 2026
One-click install
npx skills add https://github.com/lotea-be/qrspi --skill qrspi-retrospective
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qrspi-retrospective
Source: https://github.com/lotea-be/qrspi/tree/main/claude/skills/qrspi-retrospective
Command: npx skills add https://github.com/lotea-be/qrspi --skill qrspi-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This retrospective skill provides a structured approach to capture friction and gaps that arise during QRSPI stage retrospectives, and translates observations into concrete edits for agent prompts, commands, and kit templates.

Core Features & Use Cases

  • Identify stage friction between prompts and execution, surfacing actionable insights.
  • Draft per-stage retro entries and consolidate lessons into openspec backlog edits.
  • Propose concrete edits to claude/agents/skills/templates and propagate them through the kit.
  • Use case: after a stage finishes, run a retro to surface issues and generate prompt and template changes for the next iteration.

Quick Start

Describe the friction observed in the just-completed stage and propose concrete edits to prompts, templates, and contributor guidance.

Frequently Asked Questions about qrspi-retrospective

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

FAQPage Schema
How do I turn retrospective observations into actionable prompt edits?

To turn retrospective observations into actionable prompt edits, document the friction observed during a stage and propose concrete changes to prompts, templates, and contributor guidance in a structured 'Proposed edits' table.

What is a retrospective workflow for capturing prompt friction?

A retrospective workflow for capturing prompt friction involves surfacing gaps between prompts and execution after a stage finishes, documenting these issues in per-stage files, and generating template changes for the next iteration.

How do I track retrospective backlog edits in an openspec workflow?

You track retrospective backlog edits in an openspec workflow by consolidating lessons learned into backlog entries, enforcing a follow-up process to apply the proposed changes, and committing them to the kit.

Can I use a structured retrospective to improve agent prompts across multiple stages?

Yes, you can use a structured retrospective to improve agent prompts across multiple stages by applying it universally to surface issues, draft per-stage retro entries, and propagate concrete edits through the kit.

What's the best way to document process gaps and template issues after a stage?

The best way to document process gaps and template issues after a stage is to enforce a structured workflow that captures friction, proposes edits to claude/agents/skills/templates, and tracks progress within the backlog.