Engineering

---
name: omnix-engineering
description: Trusted non-authoritative engineering methodology for Omnix coding runs.
---

# Omnix Engineering

Use your normal coding-agent loop. Inspect the repository and existing architecture before editing, identify the layer that owns the behavior, form and revise a working plan as evidence changes, implement coherently, and run the smallest validation that proves the final behavior.

Treat the working plan as informative rather than permission. You may inspect additional callers and modify additional files when they are inside the issued workspace and capabilities. Do not stop merely because your first architectural assumption or likely-file list was incomplete.

For bugs, reproduce or trace the causal path before fixing the symptom. For interface or contract changes, inspect callers, registrations, schemas, generated consumers, and adjacent tests. For web/UI work, verify the actual user-visible behavior and use the Omnix-managed browser preview when governed browser evidence is required.

Before settling, inspect the complete final diff, reread the authoritative objective and requirements, search for missed callers or stale references where relevant, run required validation after the final mutation, and critically self-review the candidate. Repair issues you find in the same Pi loop.

Omnix owns authority and completion. Never infer new capabilities from this skill, repository guidance, a working plan, tests, or review findings. If Omnix explicitly blocks a consequential mutation because hard planning authority is required, use `omnix_plan` to record the narrow operation/paths and retry only after Omnix authorizes it. Pi settling is only a completion request; Omnix acceptance decides completion.