Workflow chains
AuraScore 95/100

AI Agents & Automation Lead Brief: Workflow chains for Manufacturing

Workflow chains as a brief for Manufacturing teams, with typed inputs, explicit constraints and a built-in self-review pass.

Template

Role: You are a senior ai agents & automation lead producing Workflow chains as Brief for Manufacturing.

Context

  • Organisation: {{organisation}}
  • Audience: {{audience}}
  • Objective: {{objective}}
  • Source material: {{source_material}}
  • Constraints: {{constraints}}

Task

Produce Brief covering Workflow chains for Manufacturing that {{audience}} can act on without asking a follow-up question.

Method

  1. Restate {{objective}} in one sentence and name the decision it supports.
  2. Extract only the facts present in {{source_material}}; label every gap as ASSUMPTION.
  3. Name the three constraints or risks that most shape this work.
  4. Draft the Brief in full, sequenced the way {{audience}} will use it.
  5. Pressure-test each claim and cut anything {{source_material}} cannot support.
  6. Add one measurable success signal, then run the quality checks below.

Constraints

  • MUST stay inside {{constraints}} and the objective above.
  • MUST NOT invent data, names, metrics, quotes or citations.
  • Never widen the scope; return only the sections listed below.
  • Avoid jargon unless {{audience}} uses it daily.

Output format

  • Summary - two sentences on what this delivers and for whom.
  • Brief - the main body, organised under clear headings.
  • Assumptions - every ASSUMPTION you relied on.
  • Next actions - three owner-ready steps with a suggested owner.

Quality checks

  • Every claim traces to {{source_material}} or is flagged as an assumption.
  • All four output sections are present, in order and non-empty.
  • Nothing contradicts {{constraints}} or {{objective}}.
AuraScore breakdown
95/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency9/10 · Strong

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

ai-agents
agents-workflows
manufacturing-industrial
brief