Roo Followup

Workflow

1. Classify response

   • If resultType=completion and needsReply=false: consider done; show completion or message to user.
   • If resultType=ask or needsReply=true: proceed to follow-up handling.
   • If resultType=none: treat as inconclusive; ask user whether to retry or stop.

2. Ask the user

   • Show question and options (if any) as a numbered list so the user can reply with a single number. Example:

     Roo follow-up question: <question>
     1) <option1>
     2) <option2>
     3) <option3>
     Reply with a number or free text (type 'stop' to abort):
     

   • If no options, still encourage concise answers (“short answer is fine”, “stop to abort”).
   • If the user declines to continue, stop.

3. Summarize prior context

   • Extract the last completion (or message if completion absent).
   • Build a brief summary: e.g., Previous result: ...
   • Append the user’s new answer: e.g., User follow-up answer: ...
   • Add intent: Continue the task based on this context.

4. Send a new Roo task

   • Call roo_task with the composed prompt:

     Previous result: <summary>
     User follow-up answer: <answer>
     Continue the task based on this context.
     

   • Record the new sessionId (this will be new each time; Roo does not support append).

5. Validate outcome

   • On new response, check resultType.
   • If still ask, loop steps 2–4.
   • If completion, present to user and confirm acceptance; if not acceptable, craft another follow-up.

Prompts / Templates

• New task prompt skeleton

  Previous result: <short summary of last completion/message>
  User follow-up answer: <user answer or chosen option>
  Continue the task based on this context.
  

• User prompt (to collect answer) — Use numbered options so the user can reply with digits only

  Roo follow-up question: <question>
  1) <option1>
  2) <option2>
  3) <option3>
  Reply with a number or free text (or type 'stop' to abort):
  

Notes & Constraints

• Do not attempt to append to an existing Roo task; always create a new roo_task.
• sessionId from the previous call is not reusable for sending answers (Roo lacks append API).
• Keep summaries short to avoid prompt bloat; only include what is needed for the next step.
• If resultType=none, confirm with the user before retrying to avoid loops.

Checklist

• Inspect resultType/needsReply.
• If ask: collect user answer; if completion: confirm sufficiency.
• Summarize prior result concisely.
• Re-send as new roo_task with summary + user answer.
• Repeat until completion is acceptable or user stops.