Figure it out

When the task matches no playbook, design one. The deliverable before any code is the workflow itself: a sequence of phases that scales rigor to the task, runs the scientific method, and leaves a decision trail a human can audit after stepping away.

Principles named in bold are in the principles skill. Call the Skill tool with principles as the first item of the task list, and read each named principle's file when you apply it.

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) whose first item is reading the principles index. Then add the phases below as todos.

Phase A: Frame

Ground first, then commit. Don't start the run until you can state:

• The definition of done as a falsifiable predicate, per Prove It Works.
• Scope, quantified: rough units and effort, plus the blockers grounding surfaced.
• The rigor level, biased high. One-way doors and high blast radius get more. Reversible low-stakes steps get less. Rigor is gates and artifacts, not "try harder".

Write the framing and its tradeoffs as the first rows of the decision log (Phase D), then start. Reversible work proceeds without waiting, per Never Block on the Human.