Oira

View saved version →

---
name: oira-work-reporting
description: Keep Oira updated on the user's coding work when they ask, as structured work updates (decisions, progress, verification, blockers, questions, next steps and explicitly deferred work) for an approved project, and import the recent work of past sessions when the member approved it. Sends no transcripts, prompts, replies, tool output or files.
---

# Oira work reporting

Four Oira tools: `oira_connection_status`, `oira_submit_work_update`,
`oira_work_update_status` and `oira_finish_history_import`. Report only when
the user asks you to keep Oira updated, for the current task or for the
approved project (their own instruction from "Set up Oira" is that ask, for
the repository it names), or asks for a progress update or a handoff;
import past work only as "Import recent work" says. Nothing is sent in the
background, and no hook or transcript upload is involved.

For the user's authorized current work, declare each distinct intended outcome
once and report only material new facts afterward. Keep work references
stable. Preserve adopted and reversed decisions, implementation, verification,
blockers, questions, accepted next actions, scope boundaries, and relevant
interface, transformation, revision and environment facts. Separate explicit
deferred work into its own declaration so Oira can retain it as upcoming work.
An unfinished task is not automatically deferred. Distinguish proposed,
accepted, attempted, implemented, tested, committed, merged and released.
Report the check and its actual result without logs. Describe uncertainty
rather than filling missing facts. Never export prompts, replies,
conversation summaries, tool traffic, files, reasoning, or credentials, and
read past sessions only for an approved history import. Run the local
outbound preflight on the exact payload before transmission; send only its
accepted output. Keep unchanged retry identities and check an uncertain send
before retrying.

## Before the first update

1. Call `oira_connection_status`. Continue only when `reporting.available` is
   true, `reporting.contract` is `oira_work_update.v2` and
   `reporting.structured_only` is true. If the Oira tools are missing or ask
   for sign-in, ask the user to sign in and wait: Codex signs in when Oira is installed; if it did not, open Settings, then MCP servers, and choose Authenticate next to `oira`. Then call `oira_connection_status` again. If the status lacks these values, this Oira server
   still runs an earlier, transcript-based edition: tell the user that
   structured reporting is not available there and send nothing. Never fall
   back to another tool or format.
2. Use exactly one `project_label` from `project_labels`. When several are
   approved, ask the user which one this work belongs to. Never infer it from
   a folder name, remote URL or list order.
3. Check that the preflight runs on this host:
   `python3 <this skill's folder>/scripts/prepare_work_update.py --new-ref`
   (on Windows, `py -3` instead of `python3`). It needs Python 3.11 or later
   and only the standard library. If `python3` is missing or reports
   `python_version_unsupported`, try `python3.13`, `python3.12` and
   `python3.11` (on Windows `py -3.13`, `py -3.12`, `py -3.11`) and use the
   first that works for every later run. If none works, tell the user that
   reporting needs Python 3.11 or later on this computer and send nothing.
   Never install anything.
4. Use that command's output as this task's `stream_ref`: one random
   reference per task in this chat, kept for the whole task. Start
   `sequence` at 1. After a lost receipt, a compaction or a restart,
   `oira_work_update_status` with the `project_label` and the `stream_ref`
   says what Oira holds of the stream (its works with their `work_handle`
   and fact handles) and where to continue (`retry`).

When `processing.state` is `parked`, updates are stored and read once the
workspace's work tracking is switched on; say so if the use

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 11 — file references are metadata, not package contents.