Back to Prompt Library
implementation
Build the application
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Build a Predictive Robot Tooling Cycle and Spares Provisioning Planner
Format
Code-aware
Lines
86
Sections
11
Linked challenge
Build a Predictive Robot Tooling Cycle and Spares Provisioning Planner
Prompt source
Original prompt text with formatting preserved for inspection.
86 lines
11 sections
No variables
1 code block
## Build
Aggregate robot tool cycle counts and trajectory execution data from MoveIt simulation logs. Plan predictive maintenance visits and generate tooling spare parts pull manifests based on cumulative usage thresholds.
## User
Robotics Maintenance Lead
## Workflow
1. Parse simulated MoveIt joint trajectory execution logs and extract tool cycle counters.
2. Calculate cumulative operational cycles and compare against manufacturer usage limit thresholds.
3. Correlate approaching end-of-life cycle limits with warehouse tooling stock levels.
4. Construct an advisory maintenance visit plan and tooling kit requisition order for approval.
## Interface
Asset health dashboard with cycle progression meters and one-click spare part kit draft reservation.
## Data
Generate synthetic JSON records representing robot trajectory execution histories and tooling usage parameters. Store in a local repository directory.
Starter examples below are synthetic. They are not downloaded records.
## Source
[MoveIt robotics](https://raw.githubusercontent.com/moveit/moveit2/main/README.md)
MoveIt trajectory planning execution logs, cycle metrics, and manipulator data limits cited in Source 1.
## Tools
anthropic-claude, pydantic, fastapi.
Anthropic Claude provides reasoning to reconcile trajectory cycle counts against maintenance manuals and stock levels.
Hosted Claude API for structured analysis of execution logs and spare parts reconciliation.
## Deliverables
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
## Acceptance
- Computes residual tool service life cycles based on simulated trajectory cycles.
- Identifies impending tooling cycle limits before emergency line stops occur.
- Produces valid spare parts draft reservation bills matching tooling revision codes.
## Starter Examples
```json
[
{
"input": {
"robot_id": "CELL_ROBOT_3",
"tool_id": "GRIPPER_PNEUMATIC_V2",
"cycles_completed": 98500,
"rated_max_cycles": 100000,
"average_cycles_per_hour": 50,
"inventory_records": [
{
"part_sku": "SEAL_KIT_GP2",
"in_stock": 3
}
],
"note": "These are simplified synthetic app records, not complete official schema files."
},
"expected_output": {
"remaining_cycles": 1500,
"estimated_hours_remaining": 30,
"replacement_urgency": "CRITICAL",
"allocated_parts": [
{
"part_sku": "SEAL_KIT_GP2",
"quantity": 1
}
],
"action_plan": "Schedule seal overhaul on CELL_ROBOT_3 during next planned shift break."
}
},
{
"input": {
"robot_id": "CELL_ROBOT_4",
"tool_id": "WELDER_TORCH_01",
"cycles_completed": 12000,
"rated_max_cycles": 80000,
"average_cycles_per_hour": 100,
"inventory_records": [
{
"part_sku": "TIP_NOZZLE_W1",
"in_stock": 10
}
],
"note": "These are simplified synthetic app records, not complete official schema files."
},
"expected_output": {
"remaining_cycles": 68000,
"estimated_hours_remaining": 680,
"replacement_urgency": "NOMINAL",
"allocated_parts": [],
"action_plan": "Maintain routine visual inspection; replacement not required."
}
}
]
```
## Safety
Maintenance planning advisory only. Requisitions are created in draft state for plant supervisor approval.
Use mock external writes. Require human review before any real deployment.Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Hold the task contract and output shape stable so generated implementations remain comparable.
Tune next
Update libraries, interfaces, and environment assumptions to match the stack you actually run.
Verify after
Test failure handling, edge cases, and any code paths that depend on hidden context or secrets.