pua

Guide systematic debugging and root cause analysis for repeated task failures.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Billkst/Causal-TabDiff --skill pua-billkst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pua
Source: https://github.com/Billkst/Causal-TabDiff/tree/main/.agents/skills/pua
Command: npx skills add https://github.com/Billkst/Causal-TabDiff --skill pua-billkst

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill tackles persistent task failures, developer stagnation, and user frustration by enforcing rigorous problem-solving methodologies and proactive engagement.

Core Features & Use Cases

  • Structured Debugging: Guides users through systematic root cause analysis for complex issues.
  • Proactive Engagement: Mandates thorough investigation and evidence-based questioning before seeking external help.
  • Performance Motivation: Employs motivational (and sometimes stern) rhetoric to overcome inertia and encourage ownership.
  • Use Case: When a complex deployment fails for the third time, this Skill will activate to force a deeper dive into logs, configuration, and potential environmental factors, rather than accepting a superficial fix or giving up.

Quick Start

Use the pua skill to debug the current task failure by following the 5-step methodology.

Frequently Asked Questions about pua

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

FAQPage Schema
How do I enforce exhaustive problem-solving when a complex deployment keeps failing?

Use structured debugging methodologies to guide systematic root cause analysis for complex issues, ensuring thorough investigation and evidence-based questioning before accepting superficial fixes or seeking external help.

Why does developer passivity lead to persistent task failures and how can I overcome it?

Overcome developer passivity and persistent task failures by enforcing proactive engagement, rigorous problem-solving methodologies, and motivational rhetoric that mandates end-to-end ownership and evidence-based questioning.

What is the best way to conduct systematic root cause analysis for code and configuration issues?

The best way to conduct systematic root cause analysis is following a structured debugging methodology that forces exhaustive problem-solving across code, config, research, and deployment tasks.

Does this structured debugging methodology work for configuration and research tasks or just code?

Yes, this structured debugging methodology works for all task types including code, configuration, research, and deployment, enforcing proactive tool usage and end-to-end ownership across the entire spectrum.

When should I trigger exhaustive problem-solving instead of seeking external help?

Trigger exhaustive problem-solving on repeated task failures, developer passivity, or user frustration, mandating thorough investigation and evidence-based questioning before seeking external help.