friction-report

Name: friction-report
Availability: InStock
Author: Generous-Corp

Analyze CI/CD pipeline failures and generate root-cause-focused friction reports.

13|1|Updated Apr 6, 2026

Search Tags:#automation #debugging #ci-cd #root-cause #process-improvement #friction

Ready to run

npx skills add https://github.com/Generous-Corp/pulp --skill friction-report-generous-corp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: friction-report
Source: https://github.com/Generous-Corp/pulp/tree/main/.agents/skills/friction-report
Command: npx skills add https://github.com/Generous-Corp/pulp --skill friction-report-generous-corp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the tendency to treat recurring technical issues as one-off annoyances, ensuring that friction is documented, analyzed for root causes, and resolved through durable mechanisms rather than temporary workarounds.

Core Features & Use Cases

Systemic Analysis: Distinguishes between one-off failures and recurring patterns that require architectural or process changes.
Constraint Discovery: Enforces a mandatory investigation into existing toolchains and design rationales to prevent dangerous or redundant fixes.
Living Documentation: Maintains a structured record of incidents in a private repository, ensuring that subsequent agents can track the resolution status of known issues.

Quick Start

Invoke the friction-report skill to analyze the current CI failure and generate a structured report in the planning friction directory.

Frequently Asked Questions about friction-report

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

FAQPage Schema

How do I analyze recurring CI/CD pipeline failures to find the root cause?▼

To analyze recurring CI/CD failures, you need a systemic root-cause analysis process that distinguishes one-off failures from architectural bottlenecks. This approach enforces investigation into existing toolchains and documented design rationales before proposing interventions.

Why does my development process keep hitting the same build process bottlenecks?▼

Development process bottlenecks recur when technical friction is treated as a one-off annoyance rather than a systemic failure. Without analyzing root causes and enforcing durable mechanisms, temporary workarounds replace permanent repository configuration fixes.

What is the best way to document technical friction in a private repository?▼

The best way to document technical friction is maintaining a structured living record of incidents in a private repository. This tracks the resolution status of known issues, ensuring subsequent agents can verify failure mechanisms and review previous constraints.

Can I automate fixes for systemic development failures without breaking existing toolchains?▼

You can automate fixes for systemic failures only after rigorous verification of existing failure mechanisms and design constraints. Constraint discovery prevents dangerous or redundant interventions by mandating investigation into the current toolchain rationale.

How do I generate a structured report for a current CI failure?▼

To generate a structured report for a CI failure, invoke a systemic analysis process that evaluates the failure against documented design rationales. This produces an actionable, root-cause-focused report stored in a designated friction directory.

When should I avoid applying temporary workarounds for recurring technical friction?▼

You should avoid temporary workarounds for technical friction when the issue represents a recurring pattern requiring architectural changes. If a failure mechanism repeats in CI/CD pipelines or build processes, systemic root-cause resolution provides durable prevention.