526c19fc21
- Persist chat stars in the operator-session registry (chat_star) so every browser/device shows the same Starred group; migrate old local stars once. - Add a compact pipeline graph shape to list responses and draw a lightweight list miniature; replace the cryptic id/version line with the stage count. - Surface OpenCode form questions as a chat card (chat_answer), replay a pending form to late subscribers, and notify for background questions. - Make the mobile dock's Search cell equal to every destination, keep the tab row visible with 100svh, and let Source use the full pane height. - Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie with Expires so Remember me survives app/link launches. - Keep shipped starters and the skill agnostic: no repository paths, project areas or personal device commands; add Diagnose/Fix and Research starters. - Refresh the installed skill and document the new browser conventions.
66 lines
3.7 KiB
Markdown
66 lines
3.7 KiB
Markdown
# 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 four stages.
|
|
|
|
| Template key | Workflow | Tools |
|
|
| --- | --- | --- |
|
|
| `task` | Complete a task, then commit it locally | Work: read/edit/shell and conditional web search/fetch; committer: read/shell |
|
|
| `review` | Read repository content and report findings | Read/glob/grep and conditional web search/fetch; no edit/shell |
|
|
| `research` | Research a question, then write a sourced report | Web search/fetch, then none |
|
|
| `three-stage` | Plan → implement → review → commit | Planner read/glob/grep + conditional web; implementer read/glob/grep/edit/shell; reviewer independent shell + conditional web; committer read/shell |
|
|
| `debug` | Diagnose → fix → verify → commit | Diagnose read/shell; fix read/edit/shell; verify read/shell; committer read/shell |
|
|
|
|
Every workflow that changes the repository ends in a **committer** stage that
|
|
commits locally and never pushes. The committer inspects `git status` and the full
|
|
diff, stages this run's change, and runs the repository's required checks before
|
|
committing. `task`, `three-stage` and `debug` follow this; `review` and `research`
|
|
change nothing and so do not commit.
|
|
|
|
Model and agent stages read the turn's `input.md` and `memory.md`, then return the
|
|
complete `output.md` markdown. The only required section is `# outcome` followed by
|
|
one declared edge word; every other heading is free-form evidence for the next stage
|
|
and the operator. See `docs/notes/stage-turns.md`.
|
|
|
|
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. The `three-stage` implementer works from the planner's research;
|
|
the reviewer is independent and checks the actual change rather than trusting a
|
|
stage summary.
|
|
|
|
No template assumes a language, framework, repository layout, device, deployment
|
|
target or notification setup, and none pushes to a remote. They read the project's
|
|
own conventions instead of naming files that only exist in one repository.
|
|
|
|
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:
|
|
|
|
```sh
|
|
pipelines new "My workflow" --template task --no-open
|
|
pipelines drafts
|
|
pipelines submit /path/printed/by/new.md
|
|
```
|
|
|
|
A draft created through the UI or `new` inherits the server's configured default
|
|
model. The checked-in files carry an example provider/model for direct file
|
|
submission; replace it with one your execution server actually supports. Provider
|
|
availability and search support must be verified on that server.
|
|
|
|
Templates do not impose a language, framework, schedule, notification setup or
|
|
deployment, and they never push to a remote. Add a schedule, notifications or a
|
|
deployment step only when your own workflow requires it.
|
|
|
|
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.
|