Files
pipelines/examples

Simple workflow templates

Five optional, technology-neutral starters. Nothing is installed as a published pipeline automatically; all templates are manual-only and have at most three stages.

Template key Workflow Tools
task Complete a task and report actual results Repository read/edit and shell
summary Summarize supplied text None
review Read repository content and report findings Read/glob/grep only
research Research a topic, then write a sourced report Web search/fetch, then none
three-stage Plan → implement → review and verify Scoped per stage

In the TUI, use :templates, choose a starter, and press s or Enter on Submit template. Type a name, press Enter to save a retained draft, then confirm publication. e Customize opens the editor picker instead. Canceling the name prompt creates nothing; canceling publication keeps the saved draft.

CLI equivalent:

pipelines new "My workflow" --template task --no-open
pipelines drafts
pipelines submit /path/printed/by/new.md

New drafts inherit the server's configured default model. The checked-in files contain a fallback model; direct file submission uses those configs as written. Provider inference and search availability must be verified on your execution server. Parsing a definition does not prove its model/tools can run.

Templates do not impose a language, framework, schedule, notification setup, commit, push, or deployment. Add those only when required by your own workflow. Removing a template from this catalog does not delete published versions, run history, retained drafts, or OpenCode sessions. Nested routing examples used for renderer regression tests live in internal/pipeline/testdata, not this catalog.