Automation Workspace Recipe

Use automation-workspace when recurring agent or script operations need runbooks, ownership, validation, and evidence trails.

Generate

node generator/create-index.mjs \
  --name "Ops Automation Index" \
  --slug ops-automation-index \
  --output ./ops-automation-index \
  --profile automation-workspace \
  --owner "Operations" \
  --services github,slack \
  --skip-install

What Gets Generated

• docs/ for automation operating notes.
• workspaces/ records for structured context and ownership.
• docs/automation-runbooks.md and .codex/automations/ for recurring operations.
• evals/ smoke tests for prompt, tool, retrieval, and output-format changes.

First Validation

cd ops-automation-index
npm install
npm run docs:build
npm run validate:workspaces

Next Steps

• Document the trigger, owner, schedule, inputs, outputs, and rollback path for each automation.
• Add evidence links for source systems the automation reads.
• Keep write actions behind explicit approval gates.
• Add smoke tests before changing prompts or tool payloads.

See Troubleshooting for common docs, validation, and deployment failures.