Create a blank Copilot Studio agent
Step 1 of 32
Action
Create a blank Copilot Studio agentExpected resultA blank Copilot Studio agent is visible in the captured Draft workspace.
Manual mode · literal browser construction
Build Supply Chain Disruption Alert Agent manually.
No PAC CLI, YAML import, or plugin architect. Follow each action and its evidence boundary, compare only the reviewed references, and stop at Draft.
Synthetic disclosure: this is qualitative workflow evidence using packaged synthetic inputs. It is not a customer KPI or a live-system result.
Progress will remain available on this page, but it will not persist after you leave.
Found something inaccurate? Use Report an issue on that step. It opens a prefilled GitHub issue for review and does not submit automatically.
Build and verify
Name Supply Chain Disruption Manual
Step 2 of 32
Action
Name Supply Chain Disruption ManualSupply Chain Disruption Manual
Expected resultThe page header shows the recorded manual build name: Supply Chain Disruption Manual.
Enter the reviewed global instructions
Step 3 of 32
Action
Enter the reviewed global instructions# Supply Chain Disruption Alert Agent — Manual Global Instructions
Use only the uploaded synthetic knowledge and operation skills. Treat every organization, person, identifier, date, measurement, status, score, cost, and recommendation as fictional pilot evidence.
## Boundaries
- Never activate a supplier, change a purchase order, reroute a shipment, contact a counterparty, or move inventory. Procurement and operations owners approve every action through authenticated systems.
- Do not browse for replacement facts or invent missing records.
- Keep public value statements qualitative; numbers belong only to the synthetic evidence.
- If a requested identifier is absent, say so rather than substituting another record.
- A model response is never evidence that an external action occurred.
## Routing
- Use **disruption dashboard** for Customer Fulfillment Lead questions like: “Which active disruption has the largest modeled impact and what is affected?”
- Use **risk assessment** for Supply Chain Planner questions like: “Why is RT-APAC-01 high risk?”
- Use **mitigation plan** for Operations Leader questions like: “Draft a DISR-002 mitigation scenario without rerouting or moving inventory.”
- Use **supplier alternatives** for Procurement Manager questions like: “Show Electronics alternatives without activating a supplier.”
- Use **root cause analysis** for Regional Retail Manager questions like: “I'm seeing unusual inventory movement at our Northwest stores. Can you help me understand what's happening?”
- Use **emergency options** for Regional Operations Director questions like: “What are our emergency options and costs?”
- Use **transfer plan** for Store Operations Manager questions like: “Approved. Execute both Seattle and the 5 additional stores.”
- Use **recovery plan** for Distribution Center Manager questions like: “Activate tracking and show me the Portland DC recovery plan.”
- Use **incident report** for Finance Business Partner questions like: “Create the executive report with financial impact.”
- Use **incident summary** for Supply Chain Director questions like: “Distribute the report and summarize what we accomplished.”
- Demo walkthrough: a Portland DC conveyor failure causes stockouts at 12 Northwest stores (143 SKUs, $84,300/week). Call the agent right away; every walkthrough operation has demo defaults. An approval ('execute', 'distribute') returns a ready-to-release draft; nothing is dispatched, notified or sent.
## Response contract
1. Lead with the specific synthetic record and operation result.
2. Explain the source evidence and material uncertainty.
3. Separate analysis or drafting from any future write action.
4. Name the authorized reviewer and approved production connection needed next.
5. End with the no-write boundary relevant to the operation.
<!-- locked-preview-anchors:start -->
## Skill routing map
Route from the user's natural-language intent to the correct skill below. Do not narrate internal retrieval, tool selection, restrictions, or implementation mechanics; present only the user-facing result.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-01` uses skill `supply-chain-disruption-alert-disruption-dashboard`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-02` uses skill `supply-chain-disruption-alert-risk-assessment`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-03` uses skill `supply-chain-disruption-alert-mitigation-plan`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-04` uses skill `supply-chain-disruption-alert-supplier-alternatives`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-05` uses skill `root-cause-analysis`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-06` uses skill `emergency-options`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-07` uses skill `transfer-plan`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-08` uses skill `recovery-plan`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-09` uses skill `incident-report`.
- `SUPPLY_CHAIN_DISRUPTION_ALERT-10` uses skill `incident-summary`.
These skill names above are the ONLY valid skill identifiers. Never invent, guess, or reference any other skill name. If the correct skill or its knowledge cannot be loaded after one retry in the same turn, say so honestly and stop. Do not answer using values you already know from these instructions or from general knowledge -- a response with no real citation is not acceptable output.
<!-- locked-preview-anchors:end -->
Expected resultThe reviewed manual/GLOBAL-INSTRUCTIONS.md policy is visible or saved without unrecorded edits.
Save the instruction policy
Step 4 of 32
Action
Save the instruction policyExpected resultThe reviewed manual/GLOBAL-INSTRUCTIONS.md policy is visible or saved without unrecorded edits.
Remove default web search
Step 5 of 32
Action
Remove default web searchExpected resultThe captured inventory no longer lists the default web-search capability.
Add knowledge: supply-chain-disruption-alert-rules-and-controls.md
Step 6 of 32
Action
Add knowledge: supply-chain-disruption-alert-rules-and-controls.mdExpected resultThe exact knowledge file linked for this step is attached under its complete filename. Wait for processing to finish before continuing. This step does not require the final inventory or prove the other uploads.
Add knowledge: supply-chain-disruption-alert-synthetic-records.md
Step 7 of 32
Action
Add knowledge: supply-chain-disruption-alert-synthetic-records.mdExpected resultThe exact knowledge file linked for this step is attached under its complete filename. Wait for processing to finish before continuing. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_disruption-dashboard_01
Step 8 of 32
Action
Add skill: aibast_disruption-dashboard_01Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_emergency-options_06
Step 9 of 32
Action
Add skill: aibast_emergency-options_06Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_incident-report_09
Step 10 of 32
Action
Add skill: aibast_incident-report_09Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_incident-summary_10
Step 11 of 32
Action
Add skill: aibast_incident-summary_10Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_mitigation-plan_03
Step 12 of 32
Action
Add skill: aibast_mitigation-plan_03Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_recovery-plan_08
Step 13 of 32
Action
Add skill: aibast_recovery-plan_08Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_risk-assessment_02
Step 14 of 32
Action
Add skill: aibast_risk-assessment_02Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_root-cause-analysis_05
Step 15 of 32
Action
Add skill: aibast_root-cause-analysis_05Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_supplier-alternatives_04
Step 16 of 32
Action
Add skill: aibast_supplier-alternatives_04Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Add skill: aibast_transfer-plan_07
Step 17 of 32
Action
Add skill: aibast_transfer-plan_07Expected resultThe linked SKILL.md appears with its frontmatter name and description. Open it and compare the complete instructions with the source file. This step does not require the final inventory or prove the other uploads.
Review model, skills, knowledge, and safety boundaries
Step 18 of 32
Action
Review model, skills, knowledge, and safety boundariesExpected resultThe screenshot visibly confirms Claude Opus 5, 10 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Review the skill list (10 skills)
Step 19 of 32
Action
Review the skill list (10 skills)Expected resultThe screenshot visibly confirms Claude Opus 5, 10 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Review the rest of the skill list
Step 20 of 32
Action
Review the rest of the skill listExpected resultThe screenshot visibly confirms Claude Opus 5, 10 rendered skills, and no tools. Knowledge is verified separately in the two knowledge-upload checkpoints.
Open a fresh Preview conversation
Step 21 of 32
Action
Open a fresh Preview conversationExpected resultA fresh Preview surface or its recorded qualitative result is visible; only the evidence file defines a pass.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-01: Customer Fulfillment Lead
Step 22 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-01: Customer Fulfillment LeadWhich active disruption has the largest modeled impact and what is affected?
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-01 with the recorded identifiers DISR-002, $3,800,000.00, SKU-1010; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-01. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-02: Supply Chain Planner
Step 23 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-02: Supply Chain PlannerWhy is RT-APAC-01 high risk?
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-02 with the recorded identifiers Asia-Pacific Primary, HIGH, Weather; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-02. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-03: Operations Leader
Step 24 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-03: Operations LeaderDraft a DISR-002 mitigation scenario without rerouting or moving inventory.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-03 with the recorded identifiers DISR-002, Draft Disruption Mitigation Scenario, no purchase order; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-03. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-04: Procurement Manager
Step 25 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-04: Procurement ManagerShow Electronics alternatives without activating a supplier.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-04 with the recorded identifiers TechSource Taiwan, due diligence, human approval; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-04. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-05: Regional Retail Manager
Step 26 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-05: Regional Retail ManagerI'm seeing unusual inventory movement at our Northwest stores. Can you help me understand what's happening?
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-05 with the recorded identifiers Portland DC, 143 products, $84,300/week; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-05. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-06: Regional Operations Director
Step 27 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-06: Regional Operations DirectorWhat are our emergency options and costs?
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-06 with the recorded identifiers Denver DC Emergency Transfer, $15,600, 3:1; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-06. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-07: Store Operations Manager
Step 28 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-07: Store Operations ManagerApproved. Execute both Seattle and the 5 additional stores.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-07 with the recorded identifiers ready to release, $24,500, $78,000; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-07. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-08: Distribution Center Manager
Step 29 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-08: Distribution Center ManagerActivate tracking and show me the Portland DC recovery plan.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-08 with the recorded identifiers Conveyor repair, 340 pending orders, Friday noon; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-08. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-09: Finance Business Partner
Step 30 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-09: Finance Business PartnerCreate the executive report with financial impact.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-09 with the recorded identifiers Executive Incident Report, $53,500, 47 minutes; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-09. A previous response must not influence the evidence.
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-10: Supply Chain Director
Step 31 of 32
Action
Pass SUPPLY_CHAIN_DISRUPTION_ALERT-10: Supply Chain DirectorDistribute the report and summarize what we accomplished.
Expected resultThe captured Preview evidence records SUPPLY_CHAIN_DISRUPTION_ALERT-10 with the recorded identifiers Crisis Response Summary, not sent, all 47 stores; do not infer results beyond it.
Before this case
Open Preview in a fresh conversation before running SUPPLY_CHAIN_DISRUPTION_ALERT-10. A previous response must not influence the evidence.
Confirm Draft and stop before publish
Step 32 of 32
Action
Confirm Draft and stop before publishExpected resultThe agent remains Draft and no Publish action is taken.
Troubleshooting
A screenshot or browserfilm frame is missing
Do not invent, recreate, or substitute an image. Keep the step open until its actual evidence is captured and reviewed. Remove --allow-pending only after all workshop evidence gates are met.
A knowledge file is still processing
Wait for ingestion to finish before Preview. A partial answer is not evidence.
A skill upload fails
Use the linked raw SKILL.md. Fix the reviewed source deliberately; do not silently skip the action.
The model differs from Easy mode
Record the substitution and stop the parity claim until Easy and Manual use the same reviewed model.
The Preview answer misses an identifier
Mark the recorded case failed, inspect instructions and inventory, then replay the exact prompt in a fresh conversation.
Should I publish?
No. Keep the same owned manual agent in Draft. Do not choose Publish as part of this tutorial.