Technical Demo

---
name: technical-demo
description: Deliver a customer-specific technical demonstration that proves relevant workflows, handles likely questions, and distinguishes configured demo behavior from product guarantees.
---
# Technical Demo

Use when this procedure is the primary professional method needed for the assignment.

## Procedure
1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using discovery notes, demo environment, product capabilities, sample data, and stakeholder priorities. Do not fill material gaps with assumptions when they can change the result.
3. Choose a realistic scenario, prepare clean data/state, rehearse proof points and failure recovery, instrument important outputs, and record unsupported requests.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

## Quality gate
The audience can see the agreed technical outcome and every claim is reproducible outside presentation theater.