figure-it-out

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

1|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/edivad1999/stuc-stack --skill figure-it-out-edivad1999
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figure-it-out
Source: https://github.com/edivad1999/stuc-stack/tree/main/skills/figure-it-out
Command: npx skills add https://github.com/edivad1999/stuc-stack --skill figure-it-out-edivad1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task matches no existing playbook—such as a large migration, an ambitious multi-part change, or work a human reviews after stepping away—this Skill designs a rigorous, auditable workflow before any code is written, so the wrong thing never gets built at scale. ## Core Features & Use Cases - Playbook Design: Decomposes work into atomic, independently-landable units sequenced riskiest-unknown-first, with verification harnesses built before features. - Hypothesis Loop: Runs each unit as an experiment with a stated hypothesis, smallest change, and a VERIFIED / NOT VERIFIED / INCONCLUSIVE verdict measured against the real artifact. - Audit Trail: Logs every decision and unit in a canonical TSV via the show-me-your-work skill, producing evidence a reviewer can re-run and trust in the PR. - Use Case: You need to migrate an API across dozens of call sites. The Skill frames a falsifiable definition of done, designs the phase list, runs each unit under the loop, and hands back a decision trail for review. ## Quick Start Ask the agent to figure it out for your large migration or multi-part change so it designs and runs an auditable playbook.

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 figure-it-out to design a playbook before writing code: it frames a falsifiable definition of done, decomposes the migration into atomic independently-landable units, and sequences them riskiest-unknown-first with verification built in.

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

Use it when the task matches no narrower playbook, or when a normally single-unit task becomes large or cross-cutting, such as a migration across many call sites. Focused single-unit tasks still route to Bug fix, Perf, or Feature playbooks.

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 so a reviewer can read it in the PR and re-run the evidence.

When should the architect skill be skipped during design?▼

Skip the architect arena for mechanical work whose shape is already concrete, such as copy-the-last-screen or smallest-diff changes. Running a second arena over a settled design is considered over-engineering under the laziness-protocol principle.