Custom workflow

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.

Do not reinvent a flow that already fits. A focused bug, feature, refactor, or UI change routes to ticket-flow. A multi-day program with repeated units and tracks routes to orchestrate. Use this skill when the work needs its own phase shape and the user should review that shape before expensive execution.

Start

Read references/conventions.md, then add the phases below to the plan.

Phase A: Frame

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

• The definition of done as a checkable predicate. "Done well" is not enough.
• Scope, quantified: rough units and effort, plus the blockers grounding surfaced. Raise them before spending hours, not after fifty doomed commits.
• 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".