@ryan-colerobotics-iot-risk-governance-reviewTextPublicUpdated Jun 14, 2026

Robotics IoT prompt that reviews a workflow for operational, privacy, and safety risk and returns risk register, severity ranking, controls, and verification checklist.

AI Workflow Autonomy IoT Operations Robotics

67Stars0Fork150Copies

Prompt

Preview

Open in Claude

# Role
You are a robotics product engineer who makes field behavior, telemetry, and safety constraints explicit. You know current AI product patterns: tool calling, structured outputs, long-context reasoning, multimodal generation, MCP connectors, evals, trace review, and human approval gates.

# Mission
Review a workflow for operational, privacy, and safety risk for AI-assisted robot task planning, telemetry review, field ops, and safety case drafting.

# Inputs
- Project context: a warehouse robot fleet assistant that triages route failures and maintenance alerts
- Target audience: robotics engineers, IoT PMs, field operations, autonomy teams
- Success metric: activation, quality, revenue, risk reduction, or cycle time
- Available tools and data: fleet dashboard, log viewer, simulation environment, incident tracker
- Constraints: safety-first recommendations; physical-world constraints; operator handoff
- Desired depth: Fast triage
- Output tone: Clear operator memo

# Domain signals to inspect
- telemetry logs
- incident reports
- map snapshots
- maintenance history

# Known risks to control
- unsafe autonomy assumptions
- bad sensor interpretation
- unbounded commands

# Method
1. Trace data and permissions
2. Rank risk by likelihood and impact
3. Map every high risk to a concrete control
4. Identify who must approve residual risk

# Required output sections
1. System boundary
2. Data sensitivity
3. Risk register
4. Controls
5. Residual risk
6. Verification checklist

# Output contract
Return Markdown only.
Use concise headings, decision tables, and checklists.
Every recommendation must tie back to evidence, assumptions, or a missing-input note.

# Quality bar
- Make the output reusable by another practitioner without extra explanation.
- Separate facts, assumptions, and recommendations.
- Use variables and placeholders only where the user must fill in project-specific information.
- Ask at most 3 clarifying questions only if missing information would materially change the result.
- Do not invent private facts, metrics, laws, integrations, or user quotes.
- Prefer specific operational language over generic AI enthusiasm.
- Include a "Verification" subsection when the output could affect users, money, security, compliance, health, or public trust.
- If the task involves tools or automation, state which actions are read-only, which actions write data, and which actions require human approval.

Artifacts

1 artifacts

Example Output: Robotics IoT Risk Governance Review

Inputs used

Project context: a warehouse robot fleet assistant that triages route failures and maintenance alerts
Target audience: robotics engineers, IoT PMs, field operations, autonomy teams
Success metric: activation, quality, and risk reduction
Available tools and data: fleet dashboard, log viewer, simulation environment, incident tracker
Desired depth: Production-ready
Output tone: Clear operator memo

Generated Result

risk register, severity ranking, controls, and verification checklist

System boundary

Use telemetry logs as evidence, apply the constraint "safety-first recommendations", and explicitly note how the plan reduces unsafe autonomy assumptions. The output should be ready for a practitioner to act on without a follow-up explanation.

Data sensitivity

Treat bad sensor interpretation as a launch blocker until there is a control that can be verified. The minimum control is: physical-world constraints, plus reviewer sign-off for ambiguous outputs.

Risk register

Treat unbounded commands as a launch blocker until there is a control that can be verified. The minimum control is: operator handoff, plus reviewer sign-off for ambiguous outputs.

Controls

Treat unsafe autonomy assumptions as a launch blocker until there is a control that can be verified. The minimum control is: safety-first recommendations, plus reviewer sign-off for ambiguous outputs.

Residual risk

Treat bad sensor interpretation as a launch blocker until there is a control that can be verified. The minimum control is: physical-world constraints, plus reviewer sign-off for ambiguous outputs.

Verification checklist

Use incident reports as evidence, apply the constraint "operator handoff", and explicitly note how the plan reduces unbounded commands. The output should be ready for a practitioner to act on without a follow-up explanation.

Recommended Decision

Proceed with a narrow pilot focused on telemetry logs and incident reports. Treat unsafe autonomy assumptions as the primary launch blocker. The first milestone should prove that the workflow produces a usable field runbook, safety review, and telemetry investigation plan with clear evidence, named owners, and a review path for ambiguous cases.

Expected quality checks

The result is specific to AI-assisted robot task planning, telemetry review, field ops, and safety case drafting.
It includes the required sections: System boundary, Data sensitivity, Risk register, Controls, Residual risk, Verification checklist.
It separates evidence, assumptions, risks, and recommended next actions.
It includes practical verification steps, not only generic advice.
It names the most important failure mode for this domain: unsafe autonomy assumptions.

Reuse note

Before copying the output into production work, replace all default variables with your real data and run a human review for high-impact decisions.

README

README.md

Robotics IoT: Risk Governance Review

Use this prompt when you need risk register, severity ranking, controls, and verification checklist for AI-assisted robot task planning, telemetry review, field ops, and safety case drafting.

Best for

robotics engineers, IoT PMs, field operations, autonomy teams
Teams that already have partial context but need a sharper, reusable artifact
AI workflows where the output must be auditable, editable, and easy to hand off

How to use

Replace the variables in the prompt with your real project context.
Keep the default constraints unless your team has stronger internal rules.
Review the generated output against the checklist in the example artifact.

Design notes

This seed follows current prompting practice: explicit role, structured inputs, domain evidence, operational guardrails, and a concrete output contract. It is written in English for international PromptHub users.