A checklist of processes worth teaching Codex

1. What makes a good process to teach

• Repeats at least once a week.
• Starts from a clear input.
• Has a few predictable steps.
• Has a completion check you can see.
• Doesn't depend on your gut feel partway through.

2. Ten processes to start with

• Checking a bug from logs and a screenshot.
• Building a content page from an existing template.
• Turning feedback into an update to a rules document.
• Checking status before publishing.
• Creating a checklist before a deploy.
• Summarizing a conversation into decision files.
• Drafting a post from existing research.
• Checking permissions for a new tool.
• Preparing a small PR with tests.
• Recreating a manual process you've already done twice.

3. Before you teach it

• Delete steps that don't connect to the outcome.
• Replace hardcoded examples with variable inputs.
• Add a completion check.
• Define where it needs to stop for approval.

4. Process template

Process name: [name]
  Trigger: when [it should run]
  
  Inputs:
  - [input 1]
  - [input 2]
  
  Steps:
  1. [step]
  2. [step]
  3. [step]
  
  Completion check:
  - [what proves the process succeeded]
  
  Stop point:
  - [what requires human approval]