> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adam.new/llms.txt
> Use this file to discover all available pages before exploring further.

# Repeat engineering work

> Reuse a clear brief, reference files, and acceptance checks across parts and revisions.

When the same job comes back with a new part or revision, keep the procedure and change the inputs. A useful reusable brief records enough detail for someone else to review the result.

## Build the brief on one representative part

Start a task with the actual source file, template, and requirements. Refine the result until the modeling steps, drawing layout, review rules, or analysis setup are appropriate for that part family.

Then ask Adam to extract the procedure:

```text title="Turn a completed task into a reusable brief" wrap theme={null}
Write a reusable brief for the work we just completed. Separate the inputs that change for each part from the fixed rules. Include required files, application and template, units, steps, output names, verification checks, and conditions that should stop the task. Record unresolved assumptions. Save it as a document I can review and reuse.
```

Review the brief before reusing it. A successful run on one part does not establish that the process handles every geometry, configuration, or drawing template.

## Keep shared context in a project

Add the brief and reference files to a [project](https://docs.adam.new/guides/projects.md). Name the current template and requirements clearly so a future task does not choose an obsolete version. Keep an example of an accepted output alongside the rules that made it acceptable.

Projects require a paid plan. Without a project, save the brief and attach it with the reference files when starting the next task. The brief is a reusable document; it does not create a saved executable workflow or automatically run against new files.

| Fixed context | Inputs that change |
| - | - |
| Drawing template and annotation policy | Part, configuration, and revision |
| Supplier's manufacturing limits | Geometry and material |
| Analysis method and reporting convention | Load case and source model |
| Required checks and output formats | Destination folder and file names |

## Run against new inputs

```text title="Apply a reviewed brief to another part" wrap theme={null}
Use the drawing brief in this project for [new part], revision [revision], configuration [configuration]. Check that its required inputs are present and that the procedure applies to this part. Create the outputs in [destination]. Report the source revision, checks performed, exceptions, and files produced.
```

For [batches](https://docs.adam.new/cad/batch-operations.md), try a representative file first and request a per-file report. For work that should run at a particular time, use [Scheduled tasks](https://docs.adam.new/guides/automations.md); connected desktop applications still need to be available when the work runs.

## Keep the procedure current

Recheck the brief when the CAD application, solver, material, supplier rule, or template changes. Preserve the source and revision for each result so you can distinguish a repeated method from a repeated assumption.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.