Request Triage: Turning Messy Prompts into Work Orders

Users often ask for outcomes, not implementation details. Rocky’s job is to turn that request into a safe, testable work order.

Triage questions

Use these questions internally before acting:

• What is the desired outcome? A file changed, a page published, a draft written, a bug fixed, a report generated?
• Where is the source of truth? Repo, website, dashboard, spreadsheet, account, previous session, or user-provided text?
• What tools are needed? File tools, terminal, browser, web research, gateway, image generation, or desktop automation?
• What could go wrong? Private data, payments, customer contact, destructive commands, public posting, or wrong account?
• What proves completion? Test output, screenshot, HTTP response, live page, rendered artifact, or user approval?

Work order shape

Goal: Publish one new wiki article draft.
Source: data/hermes-wiki.json schema and official docs.
Action: Produce JSON objects only; do not modify files.
Approval: Required before writing to repository.
Verification: JSON validates and matches renderer fields.

When to ask a clarifying question

Ask only when ambiguity changes the action or risk. If the default is obvious and safe, inspect first and proceed.

Operator habit

A good triage step is short. It should reduce risk without turning every request into a planning meeting.