Architect

Sketch types, function signatures, table shapes, and module boundaries with not implemented bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch.

Principles named in bold are in the principles skill: call the Skill tool with principles once, then read each named principle's file.

Start

Open a task list (your harness's task tool, or a checklist file at ~/.local/state/ox/checklists/<repo>-<branch>.md when it has none) with one entry per phase before starting.

Ground
Sketch
Agree
Implement
Scrap

Phase A: Ground the problem

Build a real mental model of every system the new code touches. Call the Skill tool with how over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation how prescribes. If the design redefines ownership or layering, also call the Skill tool with why on the existing shape so the rationale becomes a constraint, not a guess.