skills/user-context/references/automation.md

# Investment Banking Automation Setup

Use this reference only when the user explicitly asks to create, inspect, update, pause, resume, or remove an Investment Banking automation, or accepts the optional automation step during saved-context onboarding.

## Default Catalog

Read `skills/user-context/plugin-author-config/automation-config.md` from the plugin root for the configured automation id, name, frequency, launcher, and canonical automation prompt. The catalog is an author-owned menu, not evidence that an automation exists.

## Setup Rules

1. Do not create an automation until the user explicitly accepts the configured launcher or directly asks for a recurring Investment Banking workflow.
2. If `automation_update` is not already available, use `tool_search` to find it.
3. Before creating an automation, inspect `$CODEX_HOME/automations/*/automation.toml` for an existing matching automation by id, name, or prompt intent. Prefer updating a matching automation over creating a duplicate.
4. Use a `heartbeat` attached to the current thread with `destination="thread"` for the default process review. Keep the first version conversational and reviewable. Do not create a detached `cron` job unless the user explicitly requests one and provides an appropriate workspace.
5. Pass cadence through the automation tool's schedule field. Keep schedule details out of the automation prompt.
6. After creation or update, use `automation_update` readback when available and record concise operational metadata under `onboarding-state.json` `automations.configured.<automation-id>`.

## Prompt Requirements

Use the configured canonical automation prompt substantially verbatim. Do not replace it with a generic reminder. Preserve these requirements:

- invokes the Investment Banking router and applies user-context preflight before substantive work;
- reviews only saved deal and tracker pointers already present;
- produces only `Upcoming Deadlines`, `Stale Sources`, and `Missing Inputs`;
- includes the deal or tracker, dated item or gap, source pointer, and as-of date when known;
- returns an honest missing-context or no-material-actions result instead of inventing follow-ups;
- does not perform broad research or draft analysis;
- does not change source systems, send messages, edit trackers, or save new durable preferences without an explicit user request;
- remains concise and scan-friendly.

## State Metadata

Store only operational metadata under `onboarding-state.json`:

```json
{
  "automations": {
    "status": "completed",
    "configured": {
      "weekly-deal-process-review": {
        "automation_id": "<automation id>",
        "name": "Weekly Investment Banking Process Review",
        "kind": "heartbeat",
        "status": "ACTIVE"
      }
    }
  }
}
```

Do not copy automation metadata into `user-context.md`. Do not treat saved metadata as proof that the live automation still exists; inspect live automation state when a user asks about status or changes.

## Cleanup

Ask for explicit confirmation before deleting, replacing, or disabling an Investment Banking automation. After an approved cleanup, update the matching operational metadata instead of silently removing the history.