Automation Design
Design reliable automation prompts and schedules.
Workflow
Identify automation type
- Choose reminder, thread follow-up, daily or weekly report, monitoring task, research digest, or workspace job.
Capture requirements
- Clarify task, schedule, timezone, output destination, source rules, language, failure behavior, and whether duplicates should be suppressed.
- Ask only when missing details would change the created automation.
Write a self-contained prompt
- Include goal, scope, sources or file boundaries, output format, quality rules, and missing-information behavior.
- Keep schedule settings separate from task instructions.
Recommend schedule
- Use human-readable schedule language unless a tool requires structured syntax.
- State the timezone explicitly.
Confirm or create
- When an automation tool is available and the user asked to create it, use the tool.
- If schedule or destination is missing, ask before creation.
Prompt Template
Task:
[What Codex should do]
Scope:
[Topics, files, repos, sources, or boundaries]
Quality rules:
- Use reliable sources or concrete local files.
- Include links or file paths.
- State uncertainty clearly.
- Avoid duplicate or low-value items.
Output:
[Markdown report, thread reply, file path, etc.]
Language and tone:
[Thai/English, concise/detailed]
Rules
- Prefer updating an existing automation over creating a duplicate.
- Use current-source tools for news, prices, laws, schedules, product releases, and other changing facts.
- Do not expose raw schedule syntax unless useful.
- Report what will happen, when it will happen, and where the result will appear.
1---2name: automation-design3description: Design Codex automations, scheduled research jobs, recurring reports, reminders, monitors, thread follow-ups, and workspace jobs. Use when the user asks to set up, improve, schedule, template, audit, or design an automation, monitor, reminder, or recurring Markdown report.4---56# Automation Design78Design reliable automation prompts and schedules.910## Workflow11121. Identify automation type13 - Choose reminder, thread follow-up, daily or weekly report, monitoring task, research digest, or workspace job.14152. Capture requirements16 - Clarify task, schedule, timezone, output destination, source rules, language, failure behavior, and whether duplicates should be suppressed.17 - Ask only when missing details would change the created automation.18193. Write a self-contained prompt20 - Include goal, scope, sources or file boundaries, output format, quality rules, and missing-information behavior.21 - Keep schedule settings separate from task instructions.22234. Recommend schedule24 - Use human-readable schedule language unless a tool requires structured syntax.25 - State the timezone explicitly.26275. Confirm or create28 - When an automation tool is available and the user asked to create it, use the tool.29 - If schedule or destination is missing, ask before creation.3031## Prompt Template3233```text34Task:35[What Codex should do]3637Scope:38[Topics, files, repos, sources, or boundaries]3940Quality rules:41- Use reliable sources or concrete local files.42- Include links or file paths.43- State uncertainty clearly.44- Avoid duplicate or low-value items.4546Output:47[Markdown report, thread reply, file path, etc.]4849Language and tone:50[Thai/English, concise/detailed]51```5253## Rules5455- Prefer updating an existing automation over creating a duplicate.56- Use current-source tools for news, prices, laws, schedules, product releases, and other changing facts.57- Do not expose raw schedule syntax unless useful.58- Report what will happen, when it will happen, and where the result will appear.
ntaffzii