db-aeon/joshu-oss/realtime-goal

Realtime Goal

Use this skill for a single owner request deferred from SMS, jChat, voice, Slack, or Telegram.

Intake turns

• Prefer finishing a request in the current conversation when it is plausibly

under one minute.

• If required information is missing, ask one focused clarification before

calling realtime_goal_defer.

• If the turn began as quick work but tools/retries make it clearly long, call

realtime_goal_defer with a self-contained objective, then return the tool's acknowledgment verbatim. Do not continue the long work in that turn.

• A reminder request ("remind me tomorrow at 9") is quick work: call

owner_reminder_create in the current turn. Do not defer it, and do not use the Hermes cronjob tool. See skill joshu-proactive, section Owner reminders.

Kanban worker turns

1. Read the complete card body and recent comments before every action.
2. Execute only that card's objective. Use reasonable defaults for low-risk

details.

1. Follow the normal action guard before consequential external writes.
2. Re-read recent comments before a consequential action and before finishing;

the owner may amend the goal while it runs.

Calendar requests

When the card books, moves, or cancels a meeting on an owner calendar (for example a request from SMS, X, LinkedIn, or Slack DMs), follow skill ea-scheduling, step "Book": check google_calendar_find_free_slots, then write with google_calendar_create_event or google_calendar_update_event. A remote meeting gets a Google Meet link. Never write calendar events in the browser. Joshu has no delete tool: for a delete or a cancel, send the owner the event title, time, and link, and the owner deletes it.

Every run ends with exactly one call

• `kanban_complete` — you have the result the owner should receive, or
• `kanban_block(reason="<question>", kind="needs_input")` — you need one specific answer from the owner.

Exiting without either (crash, giving up, running out of ideas) is a failure: Hermes parks the card with no question, and Joshu restarts it with a `Joshu recovery` note. When you see that note, continue from where the last run stopped and end properly this time.

Asking the owner (kanban_block)

• Call kanban_block with kind="needs_input". The block reason is the question; the broker sends it to the owner.
• Ask one concise question the owner can answer in a sentence. Name the

options when there are options.

• Never ask for anything already on the card — the original request, owner

updates, and earlier answers are all there. Re-read before asking.

• Never ask the owner for a file that an email of the owner has as an

attachment. When an email says "attached" or the mail mirror lists **Attachments:**, call gmail_fetch_attachment (skill joshu-mail, section "Attachments") first. Ask only when the tool returns an error or the message has no attachment.

• Never block with a generic "need more information". Say exactly what is

missing and why.

• Presenting a menu or asking the owner to choose (options, rates, times,

confirmations) is a block, not a completion. The card stays open until the owner picks.

After the owner answers

The broker appends an `Owner answer` section with your question (You asked:) and the reply (Owner replied:).

• Continue from where you stopped using that answer. Do not repeat finished

work or re-ask the question.

• If the reply picks one of the options you offered, proceed with that option.

Only re-open a broad search if that option turns out to be unavailable, and then ask a new question.

• If a Joshu recovery note says you re-asked an answered question, use the

answer shown there.

Completing (kanban_complete)

Call kanban_complete only when handing off a checkout/approval link or reporting a truly finished outcome (done, confirmed, delivered artifact). The summary is the message the owner receives:

• Write it as a short text to them, not an internal note.
• Put each fact on its own line and any handoff URL on its own line.
• Use ASCII ("to", "-"), not arrows.
• Never say "the owner", "handed to the owner", or "at the handoff link" without

pasting the URL. Leave out CAPTCHA and tool-run notes.

Never send the completion directly. Joshu's durable delivery layer returns it to the originating channel.

Treat cancellation or an archived task as terminal. Stop work immediately and do not perform further side effects.