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
Adds an interview-driven assistant skill for customers running on
Kubernetes who are getting started with Antithesis. Bridges the gap
between antithesis-research and antithesis-setup for k8s users —
neither the customer's engineering team nor the Antithesis engagement
team typically has full context on the customer's cluster setup, and
the existing flow degenerates into a slow telephone game between them.
The skill works collaboratively with the customer to figure out their
SUT, dependencies, and stub strategy through horizontal and vertical
minimization passes. Produces a structured ops-questions document the
customer can paste into Slack, plus an escalation packet for the
Antithesis engagement team when stuck. Output is a final report under
antithesis/scratchbook/k8s-minimization.md plus working artifacts
under antithesis/scratchbook/k8s-minimization-work/.
Setup-side k8s support is a separate effort — until it lands, the
skill's final report serves as a structured handoff packet for the
Antithesis engagement team rather than a direct setup input.
The skill is more experimental than its peers in this repo: unlike
the others, it can't be dogfooded without a real customer engagement.
The README NOTE block flags this and asks for aggressive feedback.
Copy file name to clipboardExpand all lines: README.md
+30-8Lines changed: 30 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,11 @@ Enable AI agents to set up Antithesis, bootstrap your first Antithesis test, lau
18
18
19
19
**`antithesis-research` produces planning artifacts that you should review carefully.**
20
20
21
+
`antithesis-k8s-onboarding-assistance` is for customers running on Kubernetes. It's an interview-driven assistant that helps the customer (and the Antithesis engagement team) figure out what's in the k8s setup, what to keep/drop/stub for testing, and produces structured questions the customer can take to their ops team. K8s customers run it before `antithesis-setup`.
22
+
23
+
> [!NOTE]
24
+
> `antithesis-k8s-onboarding-assistance` is more experimental than the other skills here. Unlike the others, we can't realistically dogfood it without a real customer engagement — we genuinely don't know how well it works in practice yet. If you use it, please file feedback aggressively. Every real engagement teaches us something we couldn't learn synthetically.
25
+
21
26
`antithesis-triage` enables agents to parse and analyze the results of your Antithesis test runs.
22
27
23
28
`antithesis-debug` enables agents to interactively debug Antithesis test runs using the [multiverse debugger](https://antithesis.com/docs/multiverse_debugging/) — inspecting container filesystems and runtime state, running shell commands, and extracting evidence from inside the Antithesis environment.
@@ -39,6 +44,8 @@ Enable AI agents to set up Antithesis, bootstrap your first Antithesis test, lau
39
44
40
45
We recommend that you run `antithesis-research`, `antithesis-setup`, and `antithesis-workload` in order and in separate fresh contexts. After running each skill review all of the changes made so far, and iterate on them before continuing to the next skill.
41
46
47
+
If your system runs on Kubernetes, run `antithesis-k8s-onboarding-assistance` before `antithesis-setup`. It works with you to figure out which parts of your production k8s setup belong in the test environment, what should be stubbed, and what to drop.
48
+
42
49
Once the harness is in place, use `antithesis-launch` to run `docker compose build`, `snouty validate`, and `snouty run` in the right order. We recommend running this after the setup and workload skills to ensure everything is working well.
43
50
44
51
Don't hesitate to run short 15-30 minute Antithesis test runs as smoke tests to ensure that the harness is working as expected.
@@ -92,6 +99,19 @@ Here's an example:
92
99
93
100
This skill implements Antithesis workloads and places all the test commands and supporting files under `antithesis/test/`, adds assertions to carefully chosen locations in the SUT.
94
101
102
+
### antithesis-k8s-onboarding-assistance
103
+
104
+
```
105
+
/antithesis-k8s-onboarding-assistance We use Kubernetes in production. Help us figure out the test environment for Antithesis.
106
+
```
107
+
108
+
This skill produces the following artifacts, relative to the project directory:
109
+
110
+
-`antithesis/scratchbook/k8s-minimization.md` — the final report describing the test environment (components, dependencies, stubs, decisions). Once setup gains k8s support, setup reads this file directly; until then, it serves as a structured handoff packet for the Antithesis engagement team.
111
+
-`antithesis/scratchbook/k8s-minimization-work/working.md` — the live decision history across passes, including reversals and open assumptions.
112
+
-`antithesis/scratchbook/k8s-minimization-work/ops-questions.md` — the current open questions for the customer's ops team, formatted for paste-into-Slack response.
113
+
-`antithesis/scratchbook/k8s-minimization-work/escalation.md` — generated on demand if the customer needs to loop in their Antithesis engagement team for help.
114
+
95
115
### antithesis-launch
96
116
97
117
```
@@ -118,14 +138,15 @@ Here are the tools each skill may invoke, so you can pre-approve them if you pre
0 commit comments