---
name: tools-pipeline
description: Use when building editor tools, importers, build scripts, content validation or automation. Starts from the team's real bottlenecks and measures time saved.
---

# Tools and pipeline

Draft from the Game studio skills library by THE DREAMING JESTER. Adapt it to your game, team and engine.

## Goal

Remove the repetitive, error-prone steps that slow the team down.

## Before you start

- Watch people work. Find the tasks that are slow, frequent or often wrong.
- Estimate the time a tool would save against the time to build and maintain it.

## Process

1. Pick the bottleneck with the best saving for the effort.
2. Build the smallest tool that removes it, inside the tools people already use.
3. Validate content at import or save time with clear, actionable error messages.
4. Make tools safe: undo, previews, dry runs and no silent destructive changes.
5. Automate builds and checks so every change is built and tested the same way.
6. Write short usage notes with examples, and show the tool to the people who will use it.
7. Measure the result: time saved, errors prevented and adoption.

## Quality bar

- People choose to use the tool without being told.
- Errors point to the exact asset and the fix.
- The tool is maintained and has an owner.

## Output

The tool or pipeline step, documentation, and a before-and-after measure.

## Avoid

- Tools built for imagined workflows.
- Validation that blocks work without explaining how to fix it.