add-scenariolisted

# Add a scenario (flow) to the Cosmos Use this skill when the user asks to "add a scenario", "add a flow", "show what happens when X", or "trace flow Y and add it". A scenario is a named, animated sequence of steps that plays end-to-end across services on the map. If the service nodes involved don't exist yet, run the `add-service` skill first — this skill assumes all `from` / `to` / `via` ids already exist in `SERVICES` / `TOPICS`. --- ## What you'll touch | File | Why | |---|---| | `src/scenarios/scenarios.ts` | Scenario entry (and Domain entry if new) | | `src/scenarios/steps/<domain>.ts` | Step entries for the flow | | `src/scenarios/data.ts` | Barrel — only if you add a new steps file | | `src/scenarios/services.ts` / `topics.ts` | Any missing services/topics | | `src/scenarios/types.ts` | Only if you need a new `Tech` variant | --- ## Step 1 — Gather the three inputs Ask the user if any are missing: 1. **Domain** — which domain does this flow belong to? Check `DOMAINS` in `src/scenarios/scenarios.ts` (the demo ships with `shopping`, `fulfillment`, `engagement`). If it doesn't fit, confirm a new domain name — you'll add a `Domain` entry too. 2. **User-facing trigger** — what action starts the flow? ("customer clicks Buy", "webhook lands", "cron fires") 3. **Done state** — what does the user see/hear when it's over? ("order confirmed banner", "email arrives", "live tracking updates") --- ## Step 2 — Trace the real flow Spawn an Explore agent (or grep yourself