---
argument-hint: "[draft] [scope: project|global] <scenario content | file path | target to update/delete>"
description: Add, update, or delete a reusable IronBee verification scenario. Delegates to the ironbee-scenario sub-agent, which authors the script against the LIVE app (by default) and saves it to the right platform's store (or finds and updates/deletes an existing one). A leading `draft` token authors from source only (no app run).
---

# IronBee — Manage scenario

Add / update / delete a reusable verification **scenario** by **delegating to the `ironbee-scenario`
sub-agent**. It owns the devtools `scenario-*` tools; you resolve the request and relay its result.
**You do not run the scenario tools yourself.**

> Argument: `$ARGUMENTS`

## Steps
1. **If the request points to a file path** (scenario content to save), read that file now with your
   file-read tool and pass its **contents** into the sub-agent's prompt (the sub-agent's `Read` is
   for project files, but pass content you already resolved to be safe). If a given path doesn't
   resolve, stop and report `scenario file not found: <path>`.
2. **Spawn** the Agent tool with `subagent_type: "ironbee-scenario"` and a prompt:
   > Operation: manage
   > Request: \<the user's request — content to add/update, or the target to update/delete>
   > Scope: \<`global` if the user asked, else `project`>
   > Mode: \<include `Mode: draft` ONLY if the user's request begins with a `draft` token (author from
   >        source only, no app run) — otherwise OMIT this line so the verifier authors against the live app>
   The sub-agent decides add vs update (it checks for an existing same-name scenario first), picks
   the right platform, authors the script — **against the live app by default** (it starts the app if
   needed, observes the real behavior, validates by running once, then cleans up — deletes any probe /
   throwaway scenarios it added and stops what it started; `draft`
   skips this) — and stamps metadata (`argsSchema` for parametric ones).
   **Delete and fuzzy-resolved update will ask you to confirm** the matched scenario first — relay
   that confirmation prompt to the user and pass their answer back.
   **Wait for the sub-agent in the same turn — do NOT background it.**
3. **Relay** the sub-agent's summary (what it created / updated / deleted, on which platform).

This is NOT a verification cycle — it submits no verdict and does not gate completion. The
per-platform "how to author scenarios" detail lives in the `ironbee-scenario` sub-agent.
