smith

Identify usability gaps in VIA sprint gates and MCP interactions with UX recommendations.

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/drusifer/via --skill smith-drusifer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith
Source: https://github.com/drusifer/via/tree/main/agents/smith.docs
Command: npx skills add https://github.com/drusifer/via --skill smith-drusifer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates software usability and sprint-gate decisions to root out UX friction and ensure consistent, user-friendly behavior across CLI and MCP surfaces.

Core Features & Use Cases

  • Provides structured, action-oriented UX feedback during user story reviews and sprint gates.
  • Documents findings with clear recommendations, acceptance criteria, and risk signals.
  • Guides product and engineering teams toward consistent experiences across CLI, MCP, and documentation surfaces.

Quick Start

Read Smith's UX framework and run a quick usability review on the current sprint plan.

Frequently Asked Questions about smith

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

FAQPage Schema
How do I conduct a usability review for CLI and MCP interactions during a sprint gate?

Conduct a usability review by evaluating sprint gates and MCP interactions to identify UX friction. This process generates structured, action-oriented feedback with acceptance criteria and risk signals to ensure consistent user experiences across CLI, MCP, and documentation surfaces.

What is the best way to improve error messages and help text for relationship syntax?

Improve error messages and help text by applying a structured UX framework that addresses guidance around relationship syntax. This approach improves user recognition and recovery across CLI, MCP, and documentation workflows.

Does this UX feedback approach work for both user story reviews and sprint gates?

Yes, this UX feedback approach works for both user story reviews and sprint gates. It evaluates software usability decisions to root out UX friction and documents findings with concrete examples and risk signals for product and engineering teams.

How do I document UX findings with acceptance criteria and risk signals?

Document UX findings by generating structured reports that include clear recommendations and acceptance criteria. This UX evaluation process identifies usability gaps in sprint gates and highlights risk signals for product and engineering teams.

When do I need a UX evaluation for CLI and documentation workflows?

You need a UX evaluation for CLI and documentation workflows when ensuring a consistent user experience across different software surfaces. It addresses error messages, help text, and guidance to improve recognition and recovery during sprint gates and MCP interactions.

What are the limitations of running a usability review on a sprint plan?

A usability review on a sprint plan is limited to identifying UX friction in VIA's sprint gates and MCP interactions. It focuses on providing UX-focused recommendations with concrete examples but does not implement the code changes itself.