Skip to main content
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:
Turn a completed task into a reusable brief
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. 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.

​
Run against new inputs

Apply a reviewed brief to another part
For batches, try a representative file first and request a per-file report. For work that should run at a particular time, use Scheduled tasks; 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.
Last modified on October 14, 2026