Stakeholder Technical Communication
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Identify the audience, decision, prior context, time horizon, and level of technical detail needed.
- Lead with the decision-relevant outcome, status, and evidence boundary.
- Separate observed fact, proposed change, ratified decision, rejected option, unresolved question, estimate, and causal claim.
- Explain tradeoffs, risks, dependencies, alternatives, and consequences in plain US English.
- Use precise units, dates, environments, versions, and source links where they affect meaning.
- Tailor depth without removing material uncertainty, dissent, or security constraints.
- Identify decisions, owners, actions, and next evidence when the audience needs them; informational updates need no invented action.
Boundaries
- Do not simplify away material risk or present estimates as measured results.
- Do not expose secrets, private paths, customer facts, or internal topology.
- Do not send, publish, or represent stakeholder approval without separate authority.
Output
Lead with the supported outcome for the named audience. An informational update
needs no manufactured decision or action request. When a decision is required,
state its owner, exact scope, evidence, tradeoffs, and consequence. Retain material
risks, dissent, uncertainty, and requested technical detail; use an appendix only
when it helps the audience access supporting evidence.
Read the original acceptance example when checking this behavior.
Example
Synthetic example; not an observed client result.
Input: Give an informational update: local tests passed; hosted checks are pending.
Output: Local checks passed. Hosted behavior is still unverified; no release decision is requested by this update.
1---2name: explain-to-stakeholders3description: "Explains technical evidence when asked for a stakeholder update, decision brief, or plain-language status; preserves the decision needed and material limitations without unnecessary approval requests."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/explain-to-stakeholders7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-operations"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Stakeholder Technical Communication1617Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1819## Workflow20211. Identify the audience, decision, prior context, time horizon, and level of technical detail needed.222. Lead with the decision-relevant outcome, status, and evidence boundary.233. Separate observed fact, proposed change, ratified decision, rejected option, unresolved question, estimate, and causal claim.244. Explain tradeoffs, risks, dependencies, alternatives, and consequences in plain US English.255. Use precise units, dates, environments, versions, and source links where they affect meaning.266. Tailor depth without removing material uncertainty, dissent, or security constraints.277. Identify decisions, owners, actions, and next evidence when the audience needs them; informational updates need no invented action.2829## Boundaries3031- Do not simplify away material risk or present estimates as measured results.32- Do not expose secrets, private paths, customer facts, or internal topology.33- Do not send, publish, or represent stakeholder approval without separate authority.3435## Output3637Lead with the supported outcome for the named audience. An informational update38needs no manufactured decision or action request. When a decision is required,39state its owner, exact scope, evidence, tradeoffs, and consequence. Retain material40risks, dissent, uncertainty, and requested technical detail; use an appendix only41when it helps the audience access supporting evidence.4243Read [the original acceptance example](references/continuity-example.md) when checking this behavior.4445## Example4647Synthetic example; not an observed client result.4849Input: Give an informational update: local tests passed; hosted checks are pending.5051Output: Local checks passed. Hosted behavior is still unverified; no release decision is requested by this update.