| name | technical-talk-workshop |
| description | Design a developer talk or workshop around one learnable technical outcome with executable exercises, timing, checkpoints, and recovery paths. |
Technical Talk Workshop
Use when this procedure is the primary professional method needed for the assignment.
Procedure
- Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
- Establish the evidence baseline using audience profile, environment setup, demo code, exercises, timing budget, and platform constraints. Do not fill material gaps with assumptions when they can change the result.
- Define audience prerequisites, structure concept-to-demo-to-practice, rehearse timing, provide fallback artifacts, and capture common questions.
- Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
- Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
- Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.
Quality gate
Participants can complete the target task and the material survives a failed live-demo dependency.