You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Save this as <code>scenarios/hello-world.json</code>. The filename (without <code>.json</code>)
48
-
becomes the scenario key used in reports and CLI commands.
30
+
From your project root, run:
49
31
</p>
32
+
<pre><code>axis init</code></pre>
50
33
<p>
51
-
A few things that make scenarios work well:
34
+
In an interactive terminal, this prompts you for the scenarios directory and which agents to
35
+
include (comma-separated, e.g. <code>claude-code,codex,gemini</code>). It then creates two files:
52
36
</p>
53
37
<ul>
54
-
<li><strong>Specific prompts</strong> -tell the agent exactly what to do. Vague prompts lead to inconsistent results.</li>
55
-
<li><strong>Observable rubric checks</strong> -each check should describe something a judge can verify from the transcript and workspace state.</li>
56
-
<li><strong>Weighted checks</strong> -distribute weight based on importance. If the file existing matters more than its content, weight it higher.</li>
38
+
<li><code>axis.config.json</code> -minimal config with your chosen scenarios path and agents.</li>
39
+
<li><code>scenarios/hello-world.json</code> -a sample scenario that asks the agent to create a file with specific content.</li>
57
40
</ul>
58
41
<p>
59
-
See <ahref="/scenarios">Writing Scenarios</a> for a deeper guide on prompts, rubrics, setup/teardown, and examples.
0 commit comments