Routine <-> Scenario Bridge¶

The Bernstein scenario library and Anthropic's Claude Code Routines complement each other: scenarios are version-controlled YAML recipes for multi-agent work, Routines are cloud-side triggers that fire prompts on schedules or GitHub events. The bridge wires them together so a team lead can author one scenario in the repo and an operator can stand up the matching Routine in about five minutes.

Two directions¶

Direction A - Scenario to Routine (export)¶

bernstein routine export <scenario-id> --repo owner/name --output ./out writes:

out/
  prompt.md          paste into the Routine prompt field
  mcp-config.json    add as an MCP connector
  env.json           env vars the Routine session needs
  setup-guide.md     step-by-step instructions
  triggers.md        recommended trigger configurations

The prompt instructs the Routine session to call bernstein_scenario, poll status, and summarise outcomes (including PR comments when a GitHub trigger supplied a pull request number).

bernstein routine provision is an interactive wrapper around the same flow that also registers the trigger id once the operator pastes it back.

Direction B - Routine to Scenario (invoke)¶

The MCP server exposes three tools:

Tool	Purpose
`bernstein_scenarios()`	List scenarios known to the local library.
`bernstein_scenario(scenario_id, context, pr_number, branch)`	Spawn one task per scenario template.
`bernstein_scenario_status(orchestration_id)`	Aggregate status of a running scenario.

Each spawned task carries metadata.scenario_id and metadata.orchestration_id so the status tool can group them.

Provisioning flow¶

team lead          bernstein           Anthropic Routines
---------          ---------           -----------------
defines    ---->   exports    ---->   trigger fires on
scenario           prompt +           GitHub event
.yaml              mcp config         ----v-----------
                                          calls
                                          bernstein_scenario()
                                          ----v-----------
bernstein orchestrates parallel
multi-agent work in worktrees

Scenarios live in templates/scenarios/. The repo currently ships eight ready-to-use templates covering:

comprehensive PR review
security-focused PR review
nightly maintenance
deploy verification
issue decomposition
docs sync
dependency audit
test coverage boost

Auto-provisioning¶

Trigger ids resolved through bernstein routine register --scenario <id> --trigger-id <tid> --repo owner/name are persisted under .sdd/routines/registry.json. When the Routine webhook arrives at the Bernstein server with the matching trigger id, the bridge looks up the binding and invokes the scenario without operator intervention.

bernstein routine bindings lists all registered bindings.