skills.rest
KYRIE66nb
KYRIE66nbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pua

Diagnose and resolve stubborn engineering tasks through structured debugging.

Updated Apr 8, 2026
Search Tags:#debugging#verification#engineering#process#proactivity#pua#owner
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill pua-kyrie66nb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pua
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.codex/skills/pua-skill
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill pua-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The PUA-driven skill provides a structured, proactive framework to overcome stalled tasks by enforcing exhaustive problem solving, ownership, and systematic debugging.

Core Features & Use Cases

  • End-to-end problem solving with proactive ownership: when tasks stall, the Skill drives investigation, multiple hypotheses, and verification.
  • Structured failure modes and flavor adaptations to escalate issues and improve delivery under pressure.
  • A repeatable playbook (three iron rules, proactivity levels, and a five-step diagnostic flow) you can apply to code, config, research, or deployment tasks.

Quick Start

Describe your current task and immediately apply the strongest PUA flavor to drive end-to-end resolution.

Frequently Asked Questions about pua

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

FAQPage Schema
How do I debug stubborn engineering failures when tasks stall and environments are problematic?▼

Debug stubborn engineering failures by applying a five-step diagnostic flow, forming multiple hypotheses, and enforcing evidence-based verification to drive stalled tasks to resolution.

What is the best structured debugging process for complex code, configuration, or deployment tasks?▼

A structured debugging process requires three iron rules, escalating proactivity levels, and systematic evidence gathering to resolve complex code, configuration, or deployment tasks.

Can I apply proactive ownership principles to research and writing tasks, not just infrastructure?▼

Yes, proactive ownership principles apply directly to research, writing, and infrastructure tasks, forcing exhaustive problem solving and structured failure mode analysis across any stalled workflow.

Does this exhaustive problem-solving approach work for persistent deployment failures and problematic environments?▼

Yes, this approach resolves persistent deployment failures and problematic environments by adapting structured failure modes and escalating proactive investigation until evidence-based verification succeeds.

Why does my engineering task keep failing despite multiple attempted fixes?▼

Your engineering task keeps failing because it lacks a systematic diagnostic flow, relying on ad-hoc attempts instead of exhaustive hypothesis testing and evidence-based verification.

What are the limitations of using a forced proactive ownership approach for everyday engineering tasks?▼

Forced proactive ownership is limited by its heavy overhead; it is designed for complex, stalled tasks rather than simple, routine engineering tasks that require quick execution.

Related Skills

Explore More Software Engineering Skills→
dtsongdtsong
1

intake-skill

Transform natural language project descriptions into structured engagement briefs.

Community
Advanced
amo-tech-aiamo-tech-ai

Testing web apps with Playwright

Automate end-to-end browser tests for web application user flows.

Community
Advanced
wjgoarxivwjgoarxiv
29

autoresearch:debug

Guide bug hunting through falsifiable hypotheses and structured investigation loops.

Community
Advanced
paopp2paopp2

Systematic Debugging

Enforces a four-phase workflow for root-cause analysis of software issues before fixes are allowed.

Community
Basic