demonstrate

Present software increments for human taste validation before promotion sign-off.

1|Updated Jul 12, 2026

Search Tags:#quality-assurance #sdlc #human-in-the-loop #uat #demonstrate #taste-surface

Ready to run

npx skills add https://github.com/SeaBrad72/sparkwright --skill demonstrate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: demonstrate
Source: https://github.com/SeaBrad72/sparkwright/tree/main/skills/demonstrate
Command: npx skills add https://github.com/SeaBrad72/sparkwright --skill demonstrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between agent-verified correctness and human-validated quality by ensuring that features with a taste-surface are reviewed by a human before promotion.

Core Features & Use Cases

Taste-Surface Detection: Identifies UI, UX, or user flows where correct code does not necessarily mean good product.
Informed Go/No-Go: Facilitates the informed half of promotion decisions by providing a tangible artifact for human reaction.
UAT Integration: Standardizes the recording of human verdicts using the project's UAT sign-off templates.

Quick Start

Use the demonstrate skill to surface the current increment for human taste judgment by framing the specific decision call and recording the verdict in a UAT sign-off.

Frequently Asked Questions about demonstrate

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

FAQPage Schema

How do I enforce human-in-the-loop validation for UI features during the promotion lifecycle?▼

Human-in-the-loop validation requires surfacing observable artifacts for user judgment before final promotion. This ensures features with a taste-surface are reviewed by a human, bridging the gap between agent-verified code correctness and human-validated product quality.

What is a taste-surface in software development and when does it need user judgment?▼

A taste-surface in software development refers to UI, UX, or user flows where correct code does not necessarily mean a good product. It requires user judgment during the promotion lifecycle to provide a tangible artifact for human reaction and informed go/no-go decisions.

How do I integrate UAT sign-off into an automated promotion lifecycle?▼

To integrate UAT sign-off into an automated promotion lifecycle, standardize the recording of human verdicts using the project's formal UAT sign-off documentation. This requires presenting visually-observable artifacts first to frame the specific decision call before recording the final verdict.

Does automated testing guarantee product quality for user-facing features?▼

Automated testing does not guarantee product quality for user-facing features because correct code does not always translate to a good user experience. Taste-surface detection identifies these subjective UI and UX areas, requiring human-in-the-loop validation before final sign-off.

When should I require visually-observable-first sequencing for feature sign-off?▼

You should require visually-observable-first sequencing for feature sign-off whenever an increment contains subjective taste-surfaces like UI or UX flows. This sequencing ensures observable artifacts are presented for human reaction before formal UAT sign-off documentation is recorded.

Can I use demonstrate for backend infrastructure changes without a user interface?▼

Using demonstrate for backend infrastructure changes without a user interface is not its primary use case. It is designed to identify taste-surfaces in UI, UX, and user flows, ensuring human judgment is applied to visually-observable artifacts rather than headless backend logic.