Files
pipelines/examples/README.md
T

1.9 KiB

Starter pipelines

Two general-purpose starters are derived from reliable operator workflows. They use the server's default provider, model and harness, so they work across repositories.

Key Pipeline Stages Teaches
research Research and report research → report Read-only evidence gathering and a separate deliverable stage
task Implement, review and land Code → Review → UIReview → Land Bounded review loops, rendered acceptance, and delivery
  • research gathers authoritative evidence without changing the workspace, then writes the requested report or artifact from that evidence.
  • task implements a repository task, sends findings back to Code for bounded correction, checks rendered changes when applicable, and commits a candidate locally. Its checks block deliberately says repository-specific delivery commands must be supplied by the operator.

No starter guesses a language, framework, build command, provider or model. Stages return Markdown and only their # outcome section is interpreted.

On a new install

A brand-new database starts with these starters as ordinary pipelines, bound to the server's default model and harness. This happens once: removing them does not bring them back, and upgrading an existing install never adds or rewrites a pipeline.

As templates

The same files are the server's template catalog: the web/app create flow, TUI :templates and pipelines templates. Choosing one creates a new pipeline through the normal create-only flow.

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

provider=default and model=default are neutral markers, not real provider or model IDs. Template creation and seeding bind them to configured defaults. Editing these files never changes existing pipelines, published versions, run history or drafts.