Strengthen template planning, reuse and independent review
This commit is contained in:
+15
@@ -100,6 +100,10 @@ Every submission, including agent-issued `submit`/`rpc`, still uses server valid
|
||||
|
||||
## Drafts in the TUI
|
||||
|
||||
The server admits one active run at a time. A new request key is rejected while
|
||||
another run is active; inspect that run and wait for it to finish. Reusing its
|
||||
original request key reattaches idempotently.
|
||||
|
||||
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
|
||||
@@ -107,6 +111,17 @@ 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.
|
||||
Starter stages use goal-appropriate tools: the task stage and the three-stage
|
||||
implementer edit and run checks, the task, planner and review stages may
|
||||
search/fetch official sources only when external knowledge is genuinely needed,
|
||||
the three-stage implementer has no web tools and follows the planner's research,
|
||||
the standalone review stage never edits or runs commands and says so explicitly,
|
||||
and the three-stage reviewer independently inspects the real changes and receives
|
||||
the planner-owned acceptance checks rather than the implementer's summary,
|
||||
approving only when the applicable acceptance checks were independently observed
|
||||
passing and no unresolved substantive issue remains. Editing a bundled template
|
||||
source changes no installed or published definition; a starter becomes an
|
||||
immutable version only after explicit authoring and publication.
|
||||
|
||||
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 a configured harness
|
||||
|
||||
Reference in New Issue
Block a user