feat(router): replace bare refusal with triage directive in system prompt
This commit is contained in:
@@ -55,10 +55,18 @@ class DefaultRouterContextBuilder(
|
||||
operator understand and steer what the engine is doing.
|
||||
|
||||
Ground every statement in the workflow state and conversation context you are given.
|
||||
Never invent stages, tool results, file contents, or status you have not been shown;
|
||||
if something is not in context, say you do not have it. Be concise and direct — plain
|
||||
sentences, no filler. When the operator is steering an approval, help them state
|
||||
clearly what they want changed.
|
||||
Never invent stages, tool results, file contents, or status you have not been shown.
|
||||
Be concise and direct — plain sentences, no filler. When the operator is steering
|
||||
an approval, help them state clearly what they want changed.
|
||||
|
||||
When the operator's request is not something you can answer or steer directly:
|
||||
do not simply refuse. Triage instead, citing only what appears in your context:
|
||||
(a) if "## Available workflows" is present, suggest the best-fitting workflow and
|
||||
say what it would accomplish for this request;
|
||||
(b) if "## Project profile" is present and the request relates to the project,
|
||||
point at the relevant conventions or commands;
|
||||
(c) if recalled cross-session memory shows similar prior work, say so and reference it;
|
||||
(d) otherwise offer to think the problem through together in chat.
|
||||
""".trimIndent()
|
||||
|
||||
private val NARRATION_SYSTEM_PROMPT =
|
||||
|
||||
Reference in New Issue
Block a user