design-agentic-ux

Designs plan, progress, approval, memory, and undo surfaces for multi-step AI agents.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-agentic-ux-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-agentic-ux
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/design-agentic-ux
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill design-agentic-ux-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents that act on a user's behalf often feel like slot machines: they act without asking, hide what they're doing, can't be stopped cleanly, and silently overwrite outputs. This Skill provides a complete design method for the surfaces of an acting AI so users always know what it will do, what it is doing, and how to stop or reverse it. ## Core Features & Use Cases - Autonomy Gate: Classifies every agent action by reversibility and blast radius to decide between autonomous action with undo, staged review, or a mandatory approval gate. - Run and control surfaces: Checklists for plan display, named-step progress, streaming latency budgets, interrupt/cancel/undo behavior, and receipts for every autonomous action. - Gates, memory, and regeneration: Five-part approval gate anatomy, review queue patterns, memory visibility and dosing rules, and version-rail regenerate affordances. - Use Case: Designing an agent that applies a supplier price list to 46 products and emails affected customers — the Skill produces a full spec covering staged edits, per-recipient send gates, a review queue for outliers, and undo receipts. ## Quick Start Ask the AI to design the plan display, approval flow, progress states, and undo behavior for an agent that performs a multi-step task on behalf of users.

Frequently Asked Questions about design-agentic-ux

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

FAQPage Schema
How do I design an approval flow for an AI agent?

Run every agent action through the Autonomy Gate: irreversible actions like sending or purchasing always get an approval gate with five parts — the ask, the why, the exact effect preview, an escape path, and an explicit commit. Reversible actions act autonomously with a receipt and undo.

How should I show progress for a long-running AI task?

Show the plan before running with at most five user-nameable steps, then use named-step status that morphs between steps rather than fake percent bars. Set explicit latency budgets and design a 'taking longer than usual' state with a cancel option for over-budget waits.

When should an AI agent act autonomously versus ask first?

Decide by reversibility times blast radius, never by model confidence. Actions the user can reverse in one step run autonomously with undo; wide-blast-radius changes go to a staged state for review; anything leaving the system boundary requires a gate.

Does this skill cover hallucination and AI error states?

No. Hallucination, uncertainty display, refusals, and error states belong to the design-ai-trust-and-failure-states skill. This skill designs the acting surfaces and hands every failure branch to that skill by name.

How do I design regenerate and version controls for AI output?

Never let regenerate silently replace output — keep a version rail with side-by-side compare and per-section keep, since users harvest pieces from multiple generations. Pin verified facts so they stay byte-identical across regenerations and place refinement controls near the output.