pua

Route tasks through adaptive flavor and method frameworks for exhaustive problem-solving.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/sherry1991/openclaw-main-workspace --skill pua-sherry1991
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pua
Source: https://github.com/sherry1991/openclaw-main-workspace/tree/main/skills/pua
Command: npx skills add https://github.com/sherry1991/openclaw-main-workspace --skill pua-sherry1991

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PUA provides a structured, flavor-driven approach to ensure high-agency problem solving, end-to-end ownership, and proactive issue resolution across complex tasks.

Core Features & Use Cases

  • Methodology routing: automatically selects flavor and approach based on task type.
  • Mandatory governance: enforces frontmatter, references, and roadmaps; reads references for protocol.
  • Narrative guidance: provides branded narration per flavor to align team tone and delivery.

Quick Start

Load the skill, review the mandated references, and begin work using the active flavor and methodology routing.

Frequently Asked Questions about pua

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

FAQPage Schema
How does methodology routing work for complex debugging and feature work?

Methodology routing automatically selects an appropriate problem-solving flavor and approach based on the specific task type. It enforces end-to-end ownership and exhaustive resolution by reading the flavor and methodology routers to guide actions across debugging, feature work, research, and deployment.

What is high-agency problem solving and when do I need it for team misalignment?

High-agency problem solving is a structured, flavor-driven approach that enforces proactive issue resolution and end-to-end ownership. You need it when managing complex tasks across teams where misalignment and verification risks are present, ensuring exhaustive problem-solving and clear delivery alignment.

How to enforce end-to-end ownership and mandatory governance for team tasks?

You enforce end-to-end ownership by applying mandatory governance protocols that require SKILL.md frontmatter with a defined name and description. The framework reads mandated references and roadmaps to guide actions, ensuring proactive issue resolution and structured delivery alignment.

Can I use narrative guidance to align team tone across different deployment flavors?

Yes, narrative guidance provides branded narration per flavor to align team tone and delivery. The framework uses an adaptive flavor and method framework to route tasks, ensuring that communication and delivery remain consistent across different deployment and debugging contexts.

Does this problem-solving framework require specific frontmatter or reference protocols?

Yes, the framework requires SKILL.md frontmatter with a defined name and description, along with mandatory reference protocols. It reads these mandated references and roadmaps to select the active flavor and methodology routing needed to guide actions.

What are the limitations of using a flavor-driven approach for research and deployment?

The flavor-driven approach requires strict adherence to mandatory governance, frontmatter, and reference protocols. If these structural requirements are not met, the methodology routing cannot effectively read the flavor routers to guide actions, limiting its applicability for research and deployment.