Templater can live inside Operon file task templates, and QuickAdd can also be useful as the capture/creation layer once the template already contains the Operon ID placeholders. The important part is that the final created note has the right Operon fields and generated IDs.
One important first step: before building templates, I’d review Operon Settings → Key mappings. Those mappings decide which property names Operon reads/writes for fields like operonId, parentTask, status, priority, dates, etc. If you customize those names, your templates should use the same visible property names, so Operon and your Markdown stay aligned from the beginning.
After that, the easiest Operon-native setup is:
- If you already have an Obsidian templates folder, go to Operon Settings → File Tasks → File Task Templates and point Operon to that folder.
- Then those templates appear inside Operon’s file task template picker.
- When you create a new file task, you can choose one of them directly.
