figure-it-out

Designs an auditable multi-phase playbook for engineering tasks matching no existing playbook.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large migrations, ambitious multi-part changes, and unattended long-running work often fit no predefined playbook, leaving engineers without a structured, auditable process. This Skill designs a bespoke workflow that scales rigor to the task and leaves a decision trail a human can review after stepping away. ## Core Features & Use Cases - Playbook Design: Frames the task with a falsifiable definition of done, quantified scope, and a rigor level, then decomposes work into atomic, independently-landable units sequenced riskiest-first. - Hypothesis Loop: Runs each unit as an experiment with a stated hypothesis, smallest change, and verification against the real artifact, producing VERIFIED, NOT VERIFIED, or INCONCLUSIVE verdicts. - Audit Trail: Logs decisions through the show-me-your-work skill and routes one-way-door design decisions through the architect skill. - Use Case: You need to migrate a large legacy subsystem with no existing playbook. Invoke this Skill to get a phased plan with verification harnesses, parallelization decisions, and a committed decision trail for PR review. ## Quick Start Ask the AI to figure out a plan for your large migration or multi-part change using the figure-it-out 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 no existing playbook?▼

Use figure-it-out to design a bespoke playbook: it frames a falsifiable definition of done, decomposes the migration into atomic landable units sequenced riskiest-first, and builds a verification harness before the work begins.

How to make a long autonomous coding run auditable?▼

The Skill logs every decision through the show-me-your-work skill as each step lands, producing a decision trail committed alongside the diff so a reviewer can audit the run in the PR after stepping away.

When should I use figure-it-out instead of a standard playbook?▼

Use it when no narrower playbook applies, such as large migrations or ambitious multi-part changes. If a bug fix, feature, or refactoring playbook already fits, prefer that instead of designing a custom workflow.

Does figure-it-out verify each change before moving on?▼

Yes. Each unit runs as an experiment verified against the real artifact before the next starts, with verdicts of VERIFIED, NOT VERIFIED, or INCONCLUSIVE. Inconclusive results are not treated as passes.

What are the limitations of the figure-it-out approach?▼

It is overkill for mechanical work whose shape is already concrete or tasks matching an existing playbook. It also depends on sibling skills like poteto-mode, architect, and show-me-your-work being available.