peerasak-u/yolo-stack/figure-it-out

Figure it out

When the task matches no playbook, design one. The first deliverable is the plan of work itself: phases a human can read, each ending in a check, with a trail they can audit after stepping away.

Add the phases below to the todolist before anything else.

Phase A: Frame

Do not start until you can state all three.

• Done. A test that can fail, checked against a real thing, per the principle-prove-it skill. "The report is good" cannot fail. "Every figure in the report ties to the ledger export of the same date" can.
• Size. How many units of work, and what could block them. Count, do not estimate from the request.
• Rigor. More for steps that cannot be undone or that many people rely on. Less for drafts. Rigor means checks and artifacts, not effort.

Show the human this framing before a long run. Work that can be undone then proceeds without further questions, per the principle-never-block-on-the-human skill.

Learn who decides what from the actual job. Use any boundaries already stated in the yolo-mode skill or this task. Prepare the work, then ask about a concrete decision when it is needed, such as who approves a payment before it is submitted. Record newly confirmed boundaries in the mode's Autonomy section with their job context. Do not make a general permissions interview a condition for starting.

Phase B: Design the steps

• Split the job into units that can each be finished and checked alone.
• Put the step most likely to fail first. A failure at step one costs less than a failure at step nine.
• Build the check before the work. Record the starting state, so each check reads as before against after.
• Write the list of steps down. That list is what the human reviews.

Add the designed steps to the todolist, then run them.

Phase C: Run

Do one unit, check it, then start the next, per the principle-sequence-verifiable-units skill. Check the produced thing, never a report about it. When a check passes too easily, suspect the check. A result is VERIFIED, NOT VERIFIED, or INCONCLUSIVE, and inconclusive is not a pass.

Phase D: Keep the trail

Log each decision as it lands with the show-me-your-work skill. Do not reconstruct the trail at the end.

Phase E: Hand back

Check the whole against the Phase A test on the real thing. If this kind of job will come again, offer the capture-playbook skill so the next run starts from written steps.

Reply: the steps you designed, the rigor level and why, the path of the trail, what is verified against the test, and what is still open.