persona-kua

Classify architectural decisions by reversibility and ADR discipline in plan reviews.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/smp4/claude-skills --skill persona-kua
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-kua
Source: https://github.com/smp4/claude-skills/tree/main/docs/dev/ideas/personas/persona-skills-context/kua-persona
Command: npx skills add https://github.com/smp4/claude-skills --skill persona-kua

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides disciplined scrutiny of architectural decisions to ensure their reversibility is understood, context is preserved, and ADR discipline accompanies every meaningful commitment so that teams can govern long-lived systems with intention.

Core Features & Use Cases

  • Decision inventory: Lists every significant decision in a plan, compares implicit versus explicit choices, and highlights missing ADR accountability.
  • Reversibility audit: Classifies decisions as cheap, expensive, or effectively irreversible and flags mismatches between perceived and real costs.
  • Context & governance review: Ensures reasoning, alternatives, consequences, radar positions, and review triggers are documented before accepting or deferring a decision.
  • Use Case: When a plan proposes adopting new infrastructure, use this persona to validate that each decision includes a reversibility class, risk rationale, and ADR link before rollout.

Quick Start

Ask Patrick Kua to review the plan, list every architectural decision, classify its reversibility, and identify where ADR discipline is missing.

Frequently Asked Questions about persona-kua

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

FAQPage Schema
How do I assess the reversibility of architectural decisions in a plan?

To assess reversibility of architectural decisions, classify each commitment as cheap, expensive, or effectively irreversible, and flag mismatches between perceived and real reversal costs during plan reviews. Ensure ADR discipline captures context, alternatives, and consequences.

What is ADR discipline and when do I need it for technical governance?

ADR discipline ensures architectural decisions capture context, alternatives, consequences, radar positions, and review triggers. It is needed for technical governance when committing to long-lived systems to preserve reasoning and document reversibility.

How do I audit an architecture plan for missing decision documentation?

Audit an architecture plan by inventorying every significant decision, comparing implicit versus explicit choices, and highlighting missing ADR accountability where context, alternatives, or reversibility classifications are absent. This validates decision quality before rollout.

Does this approach work for reviewing infrastructure adoption plans?

Yes, this approach works for infrastructure adoption plans. It validates that each decision includes a reversibility class, risk rationale, and ADR link before rollout, ensuring new infrastructure commitments are governed with intention and documented properly.

What are the limitations of classifying decisions by reversibility class?

A limitation of classifying decisions by reversibility is that it requires complete plan documentation; if implicit choices or missing context exist in the ADR, the reversibility audit cannot accurately evaluate the true cost of reversing architectural commitments.