figure-out

figure-out is a skill for Claude Code from doodledood/manifest-dev. It costs 78 tokens per session (5,681 once invoked), scanned A, original, MIT.

A guided discussion process for understanding a problem, decision, or idea before acting on it. It tests assumptions, keeps competing explanations visible, and continues until the situation is clear enough to share.

In plain words
What is it for?
Use it to investigate a difficult topic, think through a decision, examine assumptions, compare possible approaches, or reach a shared understanding before implementation.
Why use it?
It helps prevent premature solutions to an unclear problem. By examining the underlying need and unresolved evidence, it reduces the chance of building the wrong thing.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the manifest-dev plugin — 22 skills shipped together

Good fit Use it to investigate a difficult topic, think through a decision, examine assumptions, compare possible approaches, or reach a shared understanding before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/doodledood/manifest-dev/figure-out
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add doodledood/manifest-dev --skill figure-out
Clone the repo
git clone --depth 1 https://github.com/doodledood/manifest-dev

Made for: Claude Code.

Or install manifest-dev, the plugin that ships this one along with the rest of its 22 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for figure-out

README.md
[![agentmods](https://agentmods.dev/badge/skills/doodledood/manifest-dev/figure-out.svg)](https://agentmods.dev/skills/doodledood/manifest-dev/figure-out)
Your own site
<a href="https://agentmods.dev/skills/doodledood/manifest-dev/figure-out"><img src="https://agentmods.dev/badge/skills/doodledood/manifest-dev/figure-out.svg" alt="Measured on agentmods" height="20"></a>
Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,681 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00078 $0.05681
Opus 5 $0.00039 $0.02840
Sonnet 5 $0.00016 $0.01136
Haiku 4.5 $0.00008 $0.00568

Measured yesterday against content hash 1c4629bd8ac4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

figure-out scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude-plugins/manifest-dev/skills/figure-out/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The loop

Press from the true root

Press the topic relentlessly and preserve every unresolved evidence, hypothesis, genuinely viable rival, commitment question, and patch of fog that could still change the Read. Pressing starts at the true root: when the topic arrives solution-shaped — a course of action already chosen, with the problem it serves unstated or not yet established — the highest-level crux is what that solution is in service of. Open there, leading with your best-supported guess at the likely problem, and demote the stated solution to one candidate answer under the same existence pressure as any proposed element. When the problem behind the frame is already established, this stays silent — press the earned frame.

Challenge structure before designing it

When the conversation turns toward a solution, establish whether each proposed requirement, component, mechanism, or process step earns its place before designing it. Keep it when its benefit justifies its cost under the goal and constraints; otherwise remove it or fold it into something simpler. Resolve that question from available evidence where possible; bring it to the user when their judgment would change the answer. A child probe may be needed to settle the parent. Apply the same test as meaningful children emerge.

Classify constraints before they prune

Stated constraints get a kindred check before they prune: when one would remove genuinely viable options and its grounding is unstated, establish what kind of claim it is — hard (owned, verified, externally imposed) or assumed (inherited, habitual, a preference in disguise) — before letting it narrow the option set. Classify, never re-litigate: a constraint established as hard prunes exactly as it should, and one whose grounding is already established needs no interrogation.

Which question next

Tackle the next load-bearing question first, preferring the highest-level unresolved crux: settle the parent question before its children, and go deeper only when the parent is resolved or a subquestion is needed to resolve it; within a level, prefer the question whose answer would shift the read most.

Read the full file on GitHub · 163 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday Changed 1c4629bd8ac4
  2. 2d ago Changed · +2 lines 4c499fa0dd81
  3. 7d ago First seen · 161 lines · 78 tokens per session scan A 322230b861f6

Subscribe to this mod's changes

figure-out is a skill published in the GitHub repository doodledood/manifest-dev (73 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 5,681 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

vertical-onboarding

Onboarding-and-switching playbook for SMB Product-Builder products. Defines the first-run experience that turns a prospect leaving an incumbent (ServiceTitan/Toast/Mindbody/Shopify/QuickBooks) into an activated user — import-first onboarding, the activation milestone, sample-data fallback, and the time-to-first-value…

avelikiy/great_cto · 111 tokens

create-handoff

Create handoff document for passing work to another session. ALWAYS use when the user says 'create a handoff', 'hand this off', 'save progress for later', 'I need to stop here', or when context usage is high (>60%) during implementation and work needs to continue in a fresh session.

coalesce-labs/catalyst · 69 tokens

setup-warp

Interactively configure Warp terminal as a Catalyst launcher. Checks Warp install, detects projects, interviews the user for display details (name/emoji/color/variants) and generates /.warp/tabconfigs/.toml files with session-naming and remote-control wiring. Idempotent — re-run to add or update projects.

coalesce-labs/catalyst · 66 tokens

morning-briefing

Generate a daily briefing markdown at thoughts/briefings/YYYY-MM-DD.md with six sections — Review yesterday, Surface decisions, Plan today, relay-dispatch candidates, Friction since last briefing, and Learnings since last briefing — synthesized from Linear, GitHub, Granola, Google Drive, Google Calendar, and the…

coalesce-labs/catalyst · 131 tokens

briefing-followup

Interactive walk-through of today's morning briefing. Loads the briefing markdown at thoughts/briefings/YYYY-MM-DD.md (built by morning-briefing), parses its decisions block, and walks the user through each open decision — approve / reject / defer, schedule a calendar entry, file a Linear ticket, launch a relay-ticket…

coalesce-labs/catalyst · 137 tokens

status

Use this skill when the user asks "where am I", "what's the current task", "what's blocking me", "show status", "what needs sign-off", or "what's next". Prints a snapshot of the active plan, gate, sign-off progress, and next action. Reads only — writes nothing.

lantisprime/claude-sdlc · 67 tokens