friction-retrospective

Analyze friction log entries across delivery artefacts to generate structured retrospective reports.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill friction-retrospective-petrsimonidesxart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: friction-retrospective
Source: https://github.com/petrSimonidesXart/xPmGateway/tree/main/.gaai/core/skills/cross/friction-retrospective
Command: npx skills add https://github.com/petrSimonidesXart/xPmGateway --skill friction-retrospective-petrsimonidesxart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans delivery artefacts to identify friction log entries, aggregates recurring patterns, and produces retrospective reports to surface systemic improvement opportunities discovered during delivery.

Core Features & Use Cases

  • Friction extraction across artefacts (impl-reports, qa-reports, and delivery)
  • Pattern detection and prioritization for memory/promotions
  • Structured retrospective reports with sections for pattern summary, high-signal events, and notes
  • Scope-controlled analysis via optional filters (epic, date_range, friction_type)

Quick Start

Trigger a retrospective analysis over the latest delivery artefacts to generate a structured retro report.

Frequently Asked Questions about friction-retrospective

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

FAQPage Schema
How do I analyze friction log entries from delivery artefacts?

To analyze friction log entries, this Skill scans implementation reports, QA reports, and delivery artefacts to extract recurring friction patterns and generate a structured retrospective report for systemic improvement.

How do I run a retrospective analysis filtered by epic or date range?

You can constrain retrospective analysis by applying an optional scope filter for epic, date range, or friction type to limit the extracted friction patterns to a specific delivery scope.

What is a friction retrospective report and what does it contain?

A friction retrospective report aggregates recurring friction patterns from delivery artefacts into pattern summaries, high-signal candidates, and non-promoting observations to surface systemic improvement opportunities.

Can I extract friction patterns from QA reports and implementation reports?

Yes, friction pattern extraction operates across implementation reports, QA reports, and delivery artefacts to identify recurring systemic issues and prepare them for memory ingestion by the Discovery agent.

How do I identify high-signal friction candidates for promotions?

High-signal friction candidates are identified by detecting and prioritizing recurring patterns across delivery artefacts, separating actionable systemic improvements from non-promoting observations in the report.

Are there limitations when analyzing friction logs without a scope filter?

Running retrospective analysis without a scope filter processes all available delivery artefacts, which may produce broad pattern summaries and reduce the focus on specific systemic improvement opportunities within a targeted epic or date range.