Skip to main content
pome scenarios lists the curated scenario catalog shipped with the CLI. Use it to discover runnable scenarios per twin and copy them into your project for editing. The catalog is the source of truth for pome scenarios and the /pome-test skill. Per-twin scenario descriptions live on each twin reference page.

​
Usage

pome scenarios [twin] [options]

​
Arguments

ArgumentRequiredDescription
[twin]NoTwin id (github, stripe, or slack). Omit to list available twins.

​
Options

FlagDefaultDescription
--copyoffCopy the twin’s runnable scenarios into the local project.
--dest <dir>./scenarios/With --copy, write into this directory instead of ./scenarios/.
--forceoffWith --copy, overwrite existing files in the destination.

​
Behavior

  • No args — prints available twins and one-line descriptions.
  • <twin> — lists runnable scenarios for that twin. Reference-only seed files (e.g. 00-default-seed.md) are skipped.
  • --copy — writes the same runnable files into ./scenarios/ (or --dest). Existing files are preserved unless --force is set.

​
Examples

# List twins
pome scenarios

# List GitHub scenarios
pome scenarios github

# Copy Stripe scenarios into the project
pome scenarios stripe --copy

# Copy into a custom directory, overwriting existing files
pome scenarios slack --copy --dest ./my-scenarios --force
After copying, run a scenario with pome run: 
pome run scenarios/01-bug-happy-path.md --agent "<your agent command>"