Stats
Actions
Tags
From ao-operator
Render AO Operator artifacts and launch the AO role team on a brief.
How this command is triggered — by the user, by Claude, or both
Slash command
/ao-operator:ao-run <brief-path-or-text> [slug]The summary Claude sees in its command listing — used to decide when to auto-load this command
# /ao-run — launch the factory Run the AO Operator factory end-to-end on the task described by `$ARGUMENTS`. Steps: 1. Resolve the brief. If `$ARGUMENTS` is a path to a markdown file, use it as `--brief`. Otherwise write the intent to a temp brief file first. 2. Pick a stable `--slug` (kebab-case). Use the second argument if provided. 3. From the ao-operator repo root, run: 4. Report the resolved provider mapping, generated artifact paths, and the STATUS / evidence outcome. Surface any concerns or blockers verbatim. Do not invent results — report exactly what `factory_run.py...
Run the AO Operator factory end-to-end on the task described by $ARGUMENTS.
Steps:
Resolve the brief. If $ARGUMENTS is a path to a markdown file, use it as
--brief. Otherwise write the intent to a temp brief file first.
Pick a stable --slug (kebab-case). Use the second argument if provided.
From the ao-operator repo root, run:
python3 scripts/factory_run.py --brief <BRIEF> --slug <SLUG> --run
Report the resolved provider mapping, generated artifact paths, and the STATUS / evidence outcome. Surface any concerns or blockers verbatim.
Do not invent results — report exactly what factory_run.py emits. If a gate
fails, stop and report the failing gate rather than continuing.
npx claudepluginhub uesugitorachiyo/ao-operator --plugin ao-operator