Agent skill · product strategy · cursor
figure-it-out
Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop, and logs decisions via show-me-your-work. Use for /figure-it-out, 'figure it out', a large migration, or when no narrower playbook applies.
Why this skill is useful
Provides a structured workflow for complex migrations and changes that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 2,555 stars on the source repository.
What this skill does
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. Start Open a todolist whose first item is to read the Principles section of the poteto-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-way-door design decisions, run the architect skill (it runs arena). Skip it for mechanical work whose shape is already concrete. A second arena over a settled design is over-engineering (the laziness-protocol principle skill). Decide what fans out. Parallelize only across seams, and give each worker its own worktree or branch (the separate-before-serializing-shared-state principle skill). Don't over-fan. Write the designed phase list down. That list is what the human reviews. Then execute the design. Add its steps to the todolist as concrete items, after the Phase C entry and before Phase D. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills cursor/figure-it-out