figure-it-out

Designs an auditable multi-phase playbook for large migrations and ambitious cross-cutting changes.

136|8|Updated May 9, 2026
One-click install
npx skills add https://github.com/Sma1lboy/rove --skill figure-it-out-sma1lboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figure-it-out
Source: https://github.com/Sma1lboy/rove/tree/main/.agents/skills/pstack/skills/figure-it-out
Command: npx skills add https://github.com/Sma1lboy/rove --skill figure-it-out-sma1lboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large migrations, ambitious multi-part changes, and long autonomous runs lack a built-in playbook, so agents either under-plan or over-engineer. This Skill designs a rigorous, auditable workflow before any code is written, so a human can review the decision trail after stepping away. ## Core Features & Use Cases - Playbook Design: Frames the task with a falsifiable definition of done, quantified scope, and a rigor level scaled to risk, then decomposes work into atomic, independently-landable units sequenced riskiest-first. - Hypothesis Loop: Runs each unit as an experiment with a stated hypothesis, minimal change, and verification against the real artifact, producing VERIFIED, NOT VERIFIED, or INCONCLUSIVE verdicts. - Audit Trail: Logs every decision and unit in a canonical TSV via the show-me-your-work skill, with evidence links a reviewer can re-run. - Use Case: Migrating an API across dozens of call sites: the Skill frames the migration, builds a verification harness from the pre-change baseline, sequences the riskiest call sites first, and commits a decision log alongside the diff for PR review. ## Quick Start Ask the agent to figure out a plan for your large migration or multi-part change, for example by saying "figure it out: migrate our codebase from the old ORM to the new one across all services".

Frequently Asked Questions about figure-it-out

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a large code migration with an AI agent?▼

Use a playbook-design workflow that frames the migration with a falsifiable definition of done, quantifies scope, decomposes the work into atomic independently-landable units, and sequences the riskiest unknowns first before writing code.

When should I use figure-it-out instead of a feature or bug-fix playbook?▼

Use it when the task matches no narrower playbook: a migration across many call sites, an ambitious multi-part change, or work a human reviews after stepping away. Focused single-unit tasks route to the Bug fix, Feature, or Perf playbooks instead.

How does the hypothesis loop verify each change?▼

Each unit states a hypothesis, makes the smallest change, and measures against the predicate on the real artifact, never a self-report. Verdicts are VERIFIED, NOT VERIFIED, or INCONCLUSIVE, and inconclusive results are not treated as passes.

What is the decision audit trail and where is it stored?▼

The audit trail is one canonical TSV logged via the show-me-your-work skill, with a row per decision and per unit and evidence as links. For ambitious work it is committed alongside the diff so a reviewer can read and re-run it in the PR.

When is the architect arena step skipped?▼

The architect arena with diverse isolated candidates and a read-only judge runs only for one-way-door design decisions. It is skipped for mechanical work whose shape is already concrete, since a second arena over a settled design is over-engineering.