INSTRUCTION DESIGN · Workflow idea

Make operating instructions structured, consistent, and easier to inspect.

For a technical team developing an automated assistant, organize system instructions into a structured XML message that can be reviewed and adapted. The format itself does not ensure correctness, interoperability, or compliance. Check that each section reflects an approved purpose, keep instructions free of secrets and personal data, validate the structure in the intended environment, and require a responsible person to test behavior before deployment.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A developer defines an instruction-writing need
Produces
A draft structured message with documented purpose, validation notes, and reviewer approval status.
Category
Reviews & approvals

01 / The starting point

A clear request.
A useful direction.

An approved assistant purpose, current requirements, and a technical reviewer

“Create structured instructions that are clear to people and safe to test in the intended setting.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps a technical team prepare system instructions in a structured XML format for review and possible integration.

  1. Define the intended purpose and audience

    Describe the assistant’s scope, users, limits, and expected outcomes.

  2. Organize approved requirements into sections

    Separate role, constraints, response expectations, and escalation guidance clearly.

  3. Check the structure and terminology

    Validate tags, nesting, completeness, and wording against the intended format.

  4. Test behavior with representative cases

    Review normal, ambiguous, and unsafe requests and note where instructions need revision.

  5. Approve before use in a live system

    Have a technical and policy owner confirm the final instructions and test results.

03 / The result

Something useful.
Something to build on.

A draft structured message with documented purpose, validation notes, and reviewer approval status.

AmbactiWorkflow folio · 5 steps

Review structured assistant instructions

Reviews & approvals · Example outcome

The handoff

A draft structured message with documented purpose, validation notes, and reviewer approval status.

Keep in mind

Structured formatting does not guarantee that instructions will be understood as intended or behave safely. Review the content and syntax, keep secrets out of prompts, test representative and adversarial cases, and require an owner to approve before deployment.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Document approved requirements and limits

Keep system purpose, prohibited behavior, and escalation expectations current.

Keep secrets and personal information out

Use approved configuration practices rather than putting credentials or private data in message text.

Validate format in the target environment

Test parsing, compatibility, and behavior with realistic example inputs.

Assign release review and change ownership

Require accountable reviewers to approve, version, and revisit instruction changes.

Keep exploring

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗