Parent issue: #443
Stage: answer-guidance
Task
Implement the next small slice for issue #443, stacked on PR #447: update the answer route prompt so when Sepo stays in answer mode for planning, discussion, ambiguity, or unsupported requests, it can teach the user concrete follow-up slash commands only when useful. Keep the behavior concise and non-boilerplate: suggest commands such as @sepo-agent /implement ..., /fix-pr ..., /review, or /orchestrate ... when the user's request naturally points to a next action, and explain briefly when Sepo intentionally stayed in answer mode because the wording was planning-shaped rather than an explicit change request. Prefer focused edits to .github/prompts/agent-answer.md and existing prompt/envelope tests such as .agent/src/__tests__/envelope.test.ts; avoid dispatch metadata plumbing or broader router changes in this slice unless a failing test shows it is necessary.
Base
Parent issue: #443
Stage: answer-guidance
Task
Implement the next small slice for issue #443, stacked on PR #447: update the answer route prompt so when Sepo stays in answer mode for planning, discussion, ambiguity, or unsupported requests, it can teach the user concrete follow-up slash commands only when useful. Keep the behavior concise and non-boilerplate: suggest commands such as
@sepo-agent /implement ...,/fix-pr ...,/review, or/orchestrate ...when the user's request naturally points to a next action, and explain briefly when Sepo intentionally stayed in answer mode because the wording was planning-shaped rather than an explicit change request. Prefer focused edits to.github/prompts/agent-answer.mdand existing prompt/envelope tests such as.agent/src/__tests__/envelope.test.ts; avoid dispatch metadata plumbing or broader router changes in this slice unless a failing test shows it is necessary.Base