Individual skill

figure-it-out

Design a rigorous custom playbook when no bundled playbook safely fits a large or unusual task. Use for cross-cutting ambiguous execution.

skills/figure-it-out/SKILL.md

Read pinned source

Source commit 79595c97d47b5400034fb985e67f1a00389a81af

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 22
Repository last updated: Nov 1, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
ai-agents Repository topic
claude-code Repository topic
codex Repository topic
coding-agents Repository topic
cursor Repository topic
pstack Repository topic
cline Repository topic
copilot Repository topic
gemini Repository topic
design Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 841 bytes

Read excerpt

# Figure It Out

1. Define the completion predicate and non-goals.
2. Inventory uncertainty. Split it into factual questions, empirical forks, product preferences, and irreversible decisions.
3. Resolve facts by investigation and empirical forks by prototype instead of asking the human when tools can decide.
4. Build a dependency graph of verifiable work units with a proof attached to every node.
5. Identify which units can safely fan out and which share mutable state.
6. Write the bespoke playbook, then execute it using existing skills rather than improvising around its gates.
7. Maintain a decision trail for work that can outlive the current session.