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, plus conditional web search/fetch
summary Summarize supplied text None
review Read repository content and report findings Read/glob/grep and conditional web search/fetch; no edit/shell
research Research a topic, then write a sourced report Web search/fetch, then none
three-stage Plan → implement → review and verify Planner read/glob/grep + conditional web; implementer read/glob/grep/edit/shell with no web (follows the planner's research); reviewer independent shell + conditional web

Web search/fetch is conditional: stages use it only when a task genuinely needs external knowledge such as accepted industry approaches, framework or library APIs, current security/compatibility guidance, or unfamiliar techniques, and they state why when no research is needed. Trivial, fully understood local edits do not force web access, and conditional research fails closed only when the required reliable evidence cannot be obtained, not merely because one search failed. The three-stage implementer has no web tools and works from the planner's research with local read/edit/shell. The three-stage reviewer is an independent quality gate: it receives the original task and the planner's plan/design/reuse targets/acceptance checks, inspects the actual changed files and runs its own checks, returns success only when the applicable acceptance checks were independently observed passing and no unresolved substantive issue remains, and otherwise rejects with concrete findings even when a stage reported success.

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. Editing these source files does not change any installed or published definition; each starter becomes an immutable version only after explicit authoring and publication. 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.