developer-quickstart-demo

name	developer-quickstart-demo
description	Create an executable developer quickstart or demo that reaches first value quickly while remaining technically honest and reproducible.

Developer Quickstart 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 current SDK/API, authentication/setup, supported versions, example repository, and expected output. Do not fill material gaps with assumptions when they can change the result.
3. Select one representative developer goal, minimize prerequisites, verify every command/API call, expose important failure states, and capture the finished proof.
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

A new developer can reproduce the demonstrated outcome from a clean environment using the published steps.