Replace niche templates with simple starters and direct template submission

This commit is contained in:
2026-10-10 02:37:31 +01:00
parent 4cae37f950
commit 7b10e3889e
38 changed files with 389 additions and 1195 deletions
+10 -2
View File
@@ -50,7 +50,7 @@ pipelines edit # fuzzy pipeline selection
pipelines edit "bug fix" # ask OpenCode what to change
pipelines edit "bug fix" "Add a review step"
pipelines new "release notes" "Summarize changes and notify my phone"
pipelines new "weekly digest" --template scheduled-summary
pipelines new "Text summary" --template summary
```
`new` opens OpenCode immediately when its name/request is omitted. The skill asks
@@ -70,7 +70,15 @@ Every submission, including agent-issued `submit`/`rpc`, still uses server valid
## Drafts in the TUI
Home's `n` / `:new` and Enter on a template first ask how to author the new
Use `:templates` for five simple, manual-only starters: task, summary, review,
research, and plan/implement/review. **Submit template** (`s` or Enter) asks for a
name without opening an editor. Enter saves a retained draft, then a separate
confirmation publishes it as a new pipeline. Esc before naming creates nothing;
Esc at publication keeps the draft. **Customize** (`e`) opens the editor picker
instead. Both paths inherit the configured default model and preserve existing
pipelines/history. The research starter requires configured web search support.
Home's `n` / `:new` and **Customize** (`e`) on a template first ask how to author the new
pipeline: **nvim** opens a retained Markdown draft file, or **OpenCode** opens
the collaborative harness with `@pipelines`. Tab/Shift+Tab or arrows select;
typing fuzzy-searches the choices; Enter launches and Esc cancels without