Q: 7
A logistics company is rolling out a standard prompt guideline pack across dev/test/prod
for multiple Copilot Studio agents. The environment is regulated with approval gates for
production changes, and you must demonstrate consistency without downtime during a
weekend change window. Teams currently mix role instructions, formatting rules, and tool
constraints in ad-hoc ways that cause inconsistent behavior.
Steps
1. Define non-negotiable policies and refusal behaviors
2. Collect representative user journeys and constraints
3. Draft reusable prompt patterns and placeholders
4. Build an evaluation pack and regression checks
What is the correct order of operations?
Options
Discussion
No comments yet. Be the first to comment.
Be respectful. No spam.