figure-it-out

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

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill figure-it-out-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: figure-it-out
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/figure-it-out
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill figure-it-out-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a task matches no existing playbook—such as a large migration across many call sites, an ambitious multi-part change, or work a human reviews after stepping away—ad-hoc execution produces unverifiable results and no decision trail. This Skill designs a rigorous, auditable workflow before any code is written. ## Core Features & Use Cases - Workflow Design: Frames the task with a falsifiable definition of done, quantified scope, and a rigor level scaled to risk, then decomposes the work into atomic, independently-landable units sequenced riskiest-first. - Hypothesis Loop: Runs each unit as an experiment—state a hypothesis, make the smallest change, verify against the predicate on the real artifact, and keep or revert based on evidence. - 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, so the human can trust the work after stepping away. - Use Case: Migrating an API across dozens of call sites: the Skill builds a verification harness from the pre-change baseline, sequences the migration units, verifies each one, and commits a decision trail alongside the diff for PR review. ## Quick Start Ask the AI to use $figure-it-out to plan and execute your large migration with a verifiable audit trail.

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 the figure-it-out workflow: frame a falsifiable definition of done, decompose the migration into atomic independently-landable units sequenced riskiest-first, and verify each unit against a baseline harness before starting the next.

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. A focused single-unit task should route to the matching narrower playbook 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. Verdicts are VERIFIED, NOT VERIFIED, or INCONCLUSIVE, and inconclusive results never count as a pass.

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

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

When is the architect skill invoked during workflow design?▼

The architect skill runs only for one-way-door design decisions, using diverse isolated candidates and a read-only judge on a different model family. It is skipped for mechanical work whose shape is already concrete to avoid over-engineering.