Demo Script

Demo Script

Prompt-first procedure: Describe the outcome you want in your agent conversation. The agent should select and load the appropriate AIWG assets, explain material changes, request any needed approval, and report verification evidence. Exact commands and flags appear only in the CLI reference.

First time using AIWG? Begin with Install, Connect, and Verify. This guide assumes AIWG is already installed, `all` is deployed for your provider, and the agent-owned context regeneration procedure has connected the agent to this project.

Use this script for a short zero-to-first-success demo.

The first AIWG demo should show one path working, not a tour of every framework. The success metric is small on purpose: one disposable project, one wizard preview, one deploy, one status probe, and one recommended next action.

We chose a disposable project because demo failures should be cheap. While a 300s walkthrough is not a full tutorial, it is enough to catch the common problem: the user is in the wrong folder, the provider was not chosen, or the probe is not ready.

Validation baseline: test this script against AIWG version 2026.5. While the demo is intentionally small, maintainers should record any issue that failed before the first status probe.

Setup

Use a disposable project with no private data.

mkdir aiwg-demo
cd aiwg-demo
git init

Script

1. Show the goal.

I want AIWG to help me start a small project without learning the whole system first.

2. Preview the wizard.

Use AIWG to complete this documented outcome: 2. Preview the wizard.
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Point out that no files were written.

3. Run the guided path.

Use AIWG to complete this documented outcome: 3. Run the guided path.
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

In automation, use:

Use AIWG to complete this documented outcome: In automation, use
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

4. Verify engagement.

Use AIWG to complete this documented outcome: 4. Verify engagement.
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Expected result: `engaged` is `true` after a successful deploy, or the probe gives the next command to run.

5. Ask for one first action.

Recommend one AIWG path for this demo project, one reason, and one fallback. Use the agent capability search and the agent stable-asset loader before recommending.

6. Stop after the first useful output.

Good demo ending:

Use AIWG to complete this documented outcome: Good demo ending
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Recovery Beats

If the demo starts in the wrong folder, use:

Use AIWG to complete this documented outcome: If the demo starts in the wrong folder, use
Have it inspect the current state, explain the plan, ask before material
changes, and report the result with verification evidence.

Then move to the project root and rerun the wizard preview.

If provider behavior is uncertain, say:

The local deployment is verified by the probe. Provider-session behavior is still tracked separately in the field-validation matrix.

This wording avoids a common problem: deployment evidence and provider-session behavior are different evidence types.