# AI agent build brief

Use this template with your team or AI assistant to specify one business workflow. No FieldSignal account is required. Use only records you are authorized to share in the chosen environment.

## Inputs

- Workflow and decision to automate:
- What starts the work and what counts as completion:
- Case records and source references:
- Information available at each decision:
- Current policy and process owner:
- Approved actions, limits and required approvals:
- Systems to read or change, documented tools and access owner:
- Person who takes over when the agent must stop:
- Development environment and test tools, if selected:
- Missing information and unresolved decisions:

## Task for the assistant

Use the supplied records to draft a development brief. Separate recorded facts, expert explanations and approved rules. Mark assumptions and missing evidence. Do not treat past behavior as permission for a future action.

Map the request through the decisions to completion or handoff. Recommend which steps need a fixed rule, an AI agent or a person. Explain the choice using the available evidence.

Describe each proposed tool action and the permission it needs. Use actual documented tool names when supplied. Otherwise mark the integration mapping as unresolved. Evidence access does not authorize changes to a business system.

Draft tests for a permitted action, missing information, missing approval and a failed tool action where relevant. Give the agent only information available at the decision. Keep evaluator expectations separate from the agent input. Label cases as observed, adapted or fictional.

Do not connect to systems, change records or deploy software as part of this brief.

## Required output

1. Workflow map: trigger, steps, decisions, completion and handoff.
2. Decision table: conditions, required information, allowed and forbidden actions, approver and source references.
3. Implementation requirements: data fields, documented tools, permissions and unresolved mappings.
4. Draft tests: input, applicable rule, required and forbidden actions, expected system state and checks for a pass. Set execution status to `not_run` unless an actual run provides evidence.
5. Open questions: missing fact or decision, consequence and owner.

## Review before implementation

The process owner approves the rules. Developers confirm the data, tools and permissions and check that each test can detect an incorrect action. Keep unresolved actions out of the implementation scope.

The brief is complete when each in-scope action has an approved rule, available inputs, a confirmed tool mapping and a test that can check its result. Completing this brief does not establish production readiness.

FieldSignal can help investigate the workflow: https://www.fieldsignal.dev/services/process-discovery/
Use a fictional public example: https://www.fieldsignal.dev/docs/#public-example
Review production readiness: https://www.fieldsignal.dev/learn/prepare-ai-for-production/