figure-it-outlisted

# 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. Bias toward more rigor. The cost of building the wrong thing dwarfs the cost of being careful. ## Start Open a todolist whose first item is to read the Principles section of the **meta-mode** skill. 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 (the **prove-it-works** principle skill). - 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". Present the framing and tradeoffs before committing to a long run. Reversible work proceeds (the **never-block-on-the-human** principle skill), but a multi-hour run earns one checkpoint. ## Phase B: Design the workflow Decompose into atomic, independently-landable units. Sequence riskiest-unknown-first. Scaffold and verification come before features (the **foundational-thinking** principle skill). - Build the verification harness before the work, with the baseline captured from the pre-change state, so the check reads as "old value vs new value". - For one